FS full: where's the beef?

[tecknojunky]

After a failed compile, I was surprised to find it was due to a full file system.

My root file system on a 10 GB partition with no X and all the GIU gear. I had a X system runned on a 10 GB drive(!) for more than a year without size problems.

It was the recently installed Nagios that was logging the same error every second or so and filled the drive (maybe it should do something like "message repeated n times", à la Metalog).

I made some clean up, but I can't interpret this discrepancy in size reporting:

If I ask the sizes with df:

[adaptr]

Check block size, inode counts and reserved space; man tune2fs and man df for how.

It may be that the block sizes used by the two utils are different; in fact, it almost seems that way.

Run

[kd03]

Another reason for such discrepency is that some process might have opened the files that you deleted. So unless those processes exit, the disk-space wont be reclaimed. Try to see if any such process is running (e.g. the program that generated the logfile) and kill it.

-k