I get robbed! Who stole my disk space?

[benito]

I list my disk

root@emma [~]# df -Th
Filesystem    Type    Size  Used Avail Use% Mounted on
/dev/sda5     ext3    7.8G  638M  6.8G   9% /
/dev/sda8     ext3     39G  4.8G   32G  14% /home
/dev/sda6     ext3    996M   36M  909M   4% /tmp
/dev/sda3     ext3    7.8G  6.6G  768M  90% /usr
/dev/sda2     ext3    9.7G 1004M  8.3G  11% /var
/dev/sda1     ext3    122M   17M  100M  14% /boot
tmpfs        tmpfs   1014M     0 1014M   0% /dev/shm
/dev/sdb1     ext3     67G  294M   63G   1% /opt/cdp-server

then show disk use for /usr

root@emma [~]# du -sh /usr
3.4G	/usr
root@emma [~]#

So, how can i fix this little problem?

[Spiral]

Occasionally extremely large files that have been recently deleted will still hold
onto their resources temporarily even though the files are deleted; this can be
discovered by running lsof (in this case, lsof +L1).

Usually, a system reboot will clear this issue.

If you are running a VPS account, they may be having quota managment
problems on the physical server machine.

[benito]

Occasionally extremely large files that have been recently deleted will still hold
onto their resources temporarily even though the files are deleted; this can be
discovered by running lsof (in this case, lsof +L1).

Usually, a system reboot will clear this issue.

If you are running a VPS account, they may be having quota managment
problems on the physical server machine.

Many thanks Spiral, +L1 shows a lot of large files deleted. There is any way to clear that w/o reboot?

[benito]

Nevermind, restarting apache do the trick.

[Spiral]

Many thanks Spiral, +L1 shows a lot of large files deleted. There is any way to clear that w/o reboot?

Reboot would be the easiest way ...

However, you could do a "ps -ef | grep ####" where #### is the PID
shown in your 'lsof' command output next to the large files to be cleared
to find out exactly what process is holding those file pointers open
and then restart that specific process or service.