From: Frank Steinmetzger <Warp_7@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Disk usage during emerge
Date: Thu, 8 Mar 2012 03:57:00 +0100 [thread overview]
Message-ID: <20120308025700.GA11477@eisen.lan> (raw)
[-- Attachment #1: Type: text/plain, Size: 1503 bytes --]
Hello list
It came to my attention that during (after) an emerge run, df reports
considerably less space available on my / than before the emerge (everything
except /home sits on the root partition). I was wondering how this comes to
be, since I have /var/tmp/portage on tmpfs.
I am in the middle of a KDE upgrade (4.8.0→4.8.1) right now and before I
started, I downloaded all distfiles and then looked at df /, it showed 1022
blocks, hence about 1 GB of free disk space. I am at package 115 out of 174
right now, and df shows a mere 389k blocks remaining.
Also before I began the emerge run, I started 'ncdu -x /' which scans all dirs
on the / partition and then I can browse through my FS hieararchy, showing the
disk usage of every directory. Now I ran the same ncdu command again in
another screen, so I can compare it with the first one.
The folders themselves have 0.1 to 0.2 GB difference between their old and new
state, and ncdu's bottom bar even shows the same values for both apparent and
real total disk usage (rounded to 0.1 GB). So what am I missing here? I
searched df's man page for something about apparent sizes/sparse files, but
then again, why would portage create such files in the first place?
Do you have any thoughts that might help me understand what I'm seeing?
--
Gruß | Greetings | Qapla'
I forbid any use of my email addresses with Facebook services.
You will find everything in an online database.
Just not what you are looking for.
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2012-03-08 2:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 2:57 Frank Steinmetzger [this message]
2012-03-08 5:38 ` [gentoo-user] Disk usage during emerge Paul Hartman
2012-03-08 6:08 ` Bryan Gardiner
2012-03-08 7:53 ` Julian Simioni
2012-03-08 7:54 ` Julian Simioni
2012-03-08 10:50 ` [gentoo-user] " Nikos Chantziaras
2012-03-08 14:55 ` Frank Steinmetzger
2012-03-08 15:56 ` Nikos Chantziaras
2012-03-08 20:01 ` Alan McKinnon
2012-03-08 23:42 ` walt
2012-03-09 0:05 ` Alan McKinnon
2012-03-09 0:28 ` Neil Bothwick
2012-03-09 0:29 ` Neil Bothwick
2012-03-09 6:38 ` Bryan Gardiner
2012-03-09 15:33 ` Paul Hartman
2012-03-09 16:45 ` Bryan Gardiner
2012-03-09 17:09 ` Mark Knecht
2012-03-10 2:46 ` Bryan Gardiner
2012-03-10 2:49 ` Bryan Gardiner
2012-03-10 19:27 ` Mark Knecht
2012-03-10 19:40 ` Mark Knecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120308025700.GA11477@eisen.lan \
--to=warp_7@gmx.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox