Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you running this as root? If not, there may be directories that you can't read and therefore the space that their contents occupy won't be included in the total.
Distribution: At home: Arch, OpenBSD, Solaris. At work: CentOS, Debian, Ubuntu
Posts: 3,625
Rep:
Possibly a program has unlinked a file in /home but still has a copy open for itself, in which case the file doesn't have a named linked on the hard drive, but the space is not yet freed. Killing the offending program would help in that case (can be accomplished via a reboot if no other way possible).
/home is 22GB, so it cannot be just one file. It must be some program which is doing this, and will do this agaiin on reboot. Any idea on how to find whos teh culprit?
I'm not sure about the file system. Most likely its some journalised filesystem
df -i gave me:
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/sda6 2.8M 611 2.8M 1% /home
Found the culprit - there was a user program that was running for a long time - a runaway process or something. I found it out as "who" did not indicate that user to be logged in, and the program (xfig) does not usually run for long, and it was consuming 20% cpu. After killing that process, I got the 22GB back.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.