determining the space used in / partition
d.hill at yournetplus.com
Mon Oct 1 22:28:09 PDT 2007
On Tue, 2 Oct 2007 at 07:23 +0200, zszalbot at gmail.com confabulated:
> Hello again,
>>> Through df I realized my / partiotion is out of space:
>>> Filesystem 1K-blocks Used Avail Capacity Mounted on
>>> /dev/ad0s1a 198126 196070 -13794 108% /
>>> devfs 1 1 0 100% /dev
>>> /dev/ad0s1e 44511308 4217762 36732642 10% /usr
>>> /dev/ad0s1d 30462636 3210580 24815046 11% /var
>>> devfs 1 1 0 100% /var/named/dev
>>> /dev/da0s1c 75685352 34308200 35322324 49% /mnt/usbck
>>> How can I determine what occupies the space in it? That is, it is not
>>> big as you can see. So I issued:
>>> du -hs /
>>> but it was taking ages (I am not sure but maybe du -hs counts all
>>> directories on the HD?
>>> Anyway, I do not really know where to look what has eaten the / space.
>>> Were it for /usr or /var, it would be obvious to me where to look for
>>> Many thanks!
>> I don't see you have defined a /tmp partition. Perhaps /tmp is taking up
>> all the space. Try:
>> du -h /tmp
>> and see how much /tmp is taking up.
> du -hs /tmp
> 1.4M /tmp
> du -hs /
> One thing that comes to my mind. Each Sunday I have a script which
> makes a full dump of the HD to a back-up USB drive. Last weekend
> someone cleaining the computer room, must have accidentally powered
> off the USB drive. As a result, the dump has not been completed
> because the USB drive was not mounted at that time. I use cron for
> this task. Does it matter could have caused this?
If the '-L' switch is used (telling dump it is dumping a live file system)
it will first dump everything into a .snap directory before performing the
dump. What does:
du -hs /.snap
give for a result?
More information about the freebsd-questions