disk usage

[Matthew Gillen]

On 11/24/2009 10:05 AM, Daniel Feenberg wrote:
> A running program that has open a deleted file will prevent the space
> occupied by the file from being returned to free space, but the file
> will not show up in "du". When the program terminates the space will be
> freed. If your reboot the space should reappear. Short of rebooting, or
> guessing, I am not sure how to determine what is using the space.

That's nasty.  Time to start murdering processes...

It doesn't appear to be any of the usual suspects (mythtv-backend,
spamassassin, sendmail, apache, nfs, cups).

Guess I'll have to reboot.  That stinks.

On 11/24/2009 10:20 AM, Jarod Wilson wrote:
>  (I'm assuming you've already looked for massive /.foo files).

Yes, definitely checked for that.  There's an .autofsck file, but nothing
else.  Perhaps something went bonkers a couple weeks ago (the creation
timestamp on that autofsck file is Nov 7), and the system said "we'll have to
fix that the next time we reboot" (hence the creation of the autofsck file),
but didn't otherwise notify me?

Thanks for insight guys,
Matt