/ file system is full, but du does not show that it's full

c0re nr1c0re at gmail.com
Thu Jan 6 12:12:02 UTC 2011


2011/1/6 Matthew Seaman <m.seaman at infracaninophile.co.uk>:
> On 06/01/2011 11:26, c0re wrote:
>> # df -h
>> Filesystem     Size    Used   Avail Capacity  Mounted on
>> /dev/ad0s1a    496M    466M   -9.8M   102%    /
>>
>> So it's full.
>>
>> But by du it's not appeared to be full
>>
>>
>> # du -hxd 1 /
>> 2.0K    /.snap
>> 512B    /dev
>> 2.0K    /tmp
>> 2.0K    /usr
>> 2.0K    /var
>> 1.9M    /etc
>> 2.0K    /cdrom
>> 2.0K    /dist
>> 1.0M    /bin
>> 131M    /boot
>>  10M    /lib
>> 356K    /libexec
>> 2.0K    /media
>>  12K    /mnt
>> 2.0K    /proc
>> 7.2M    /rescue
>> 296K    /root
>> 4.7M    /sbin
>> 4.0K    /lost+found
>> 157M    /
>>
>
> Do you have partitions mounted at /tmp, /usr, /var etc?  Does the output
> of your du command change if you unmount those partitions?
> (It might be an idea to boot into a livefs CD or DVD given that du(1)
> lives in /usr/bin, so a bit tricky to unmount /usr and then run du)
>
> My guess is that you've at one time created files beneath what is
> usually a mount point.  Mounting the partition over them makes those
> files inaccessible, but they still take up space on the drive.
>
>        Cheers,
>
>        Matthew
>
> --
> Dr Matthew J Seaman MA, D.Phil.                   7 Priory Courtyard
>                                                  Flat 3
> PGP: http://www.infracaninophile.co.uk/pgpkey     Ramsgate
> JID: matthew at infracaninophile.co.uk               Kent, CT11 9PW
>
>

Nice idea! But I can't check it now - server is may hundred km away
and no KVM aviable. Will check it 1 or 2 weeks later. Checked only
/tmp - it was ok, no files there after unmount.


More information about the freebsd-questions mailing list