You are not currently logged in. If you do not have a user account then please consider creating one and logging in before you post your comment. This will allow you to track replies to your comment, and take part in the site much more freely.

To add your comment, fill in all the boxes below and then preview it to make sure you're happy with the way that it looks.

This is the comment you were replying to, attached to the article Keeping track of disk space:

#5 Re: Keeping track of disk space Posted by stevenothing (81.6.xx.xx) on Sat 21 May 2005 at 11:59 May also be worth mentioning about those times when you see a massive disparity between the results of a df and a du. You don't seem to be using up that much space, but you hardly have any free either. This is often down to long running processes keeping their file handles open (in my experience, often caused by logrotate not doing a restart properly). These can be found with lsof | grep deleted Easiest way to free up the space is to simply restart the process that is holding the filehandle open. Few other useful things I've found for tracking down large files: find /home/ -size +100000k to look for large files, and: find /home -size +100000k -ls | sort -n -k7,7 To get the same results sorted. Installing quotas can also be useful, as it allows you to see what users are using up lots of space instantly, instead of waiting for a recursive du process, which on large drives can take ages. Downside to this method being that you then have to deal with quotas, which can be undesirable (as in a recent accident whereby vpopmail user accidentally got a quota of about 500Mb on a machine with 800+ users...)

Inappropriate comments will be removed.

Username:

Password:

[ Advanced Login ]

Register Account