1 |
Hello list |
2 |
|
3 |
It came to my attention that during (after) an emerge run, df reports |
4 |
considerably less space available on my / than before the emerge (everything |
5 |
except /home sits on the root partition). I was wondering how this comes to |
6 |
be, since I have /var/tmp/portage on tmpfs. |
7 |
|
8 |
I am in the middle of a KDE upgrade (4.8.0→4.8.1) right now and before I |
9 |
started, I downloaded all distfiles and then looked at df /, it showed 1022 |
10 |
blocks, hence about 1 GB of free disk space. I am at package 115 out of 174 |
11 |
right now, and df shows a mere 389k blocks remaining. |
12 |
|
13 |
Also before I began the emerge run, I started 'ncdu -x /' which scans all dirs |
14 |
on the / partition and then I can browse through my FS hieararchy, showing the |
15 |
disk usage of every directory. Now I ran the same ncdu command again in |
16 |
another screen, so I can compare it with the first one. |
17 |
|
18 |
The folders themselves have 0.1 to 0.2 GB difference between their old and new |
19 |
state, and ncdu's bottom bar even shows the same values for both apparent and |
20 |
real total disk usage (rounded to 0.1 GB). So what am I missing here? I |
21 |
searched df's man page for something about apparent sizes/sparse files, but |
22 |
then again, why would portage create such files in the first place? |
23 |
|
24 |
Do you have any thoughts that might help me understand what I'm seeing? |
25 |
-- |
26 |
Gruß | Greetings | Qapla' |
27 |
I forbid any use of my email addresses with Facebook services. |
28 |
|
29 |
You will find everything in an online database. |
30 |
Just not what you are looking for. |