disk usage monitor figures don't add up?

Joel Jaeggli joelja at darkwing.uoregon.edu
Fri Dec 10 02:06:15 UTC 2004


response at bottom...

On Thu, 9 Dec 2004, Gene Heskett wrote:

> Greetings;
>
> I need a bit of help from the ext3 filesystem folks I think.   I'm
> haveing a comprehension problem here.  A snip from a df report:
>
> /dev/hdd3      176100712   165509176   26340  100.3% /amandatapes
>
>> From the above, there is about 10GB on the missing list!  Amanda just
> bailed out early because the disk was full, while the 2 figures on
> the left claimed there should have been somewhere between 10GB and
> 11GB of space left, not the 26 megs shown above.
>
> The output of a du . on that partition, before I ran the amflush, was
> 165509176 bytes total used out of 176100712 that df claimed it has
> for a total, both in 1024 byte kilobytes.
>
> So my question is: Where is the math broken?  Both du and df, or my
> head?
>
> Surely there cannot be 10+GB tied up in inodes and journals?

Under normal circumstance an ext3 filesystem has about 5% reserved space 
which only root can touch. On very large filesystems that can be a little silly, you can change the 
number of reserved blocks with tune2fs. some apps will omit the reserved 
space in making calculations.

>

-- 
-------------------------------------------------------------------------- 
Joel Jaeggli  	       Unix Consulting 	       joelja at darkwing.uoregon.edu 
GPG Key Fingerprint:     5C6E 0104 BAF0 40B0 5BD3 C38B F000 35AB B67F 56B2




More information about the fedora-list mailing list