/home partition mysteriously filling up
I have a strange problem. Recently, I started getting strange errors saying that things could not be saved in my home directory, and quickly checked with df. . Here is what I get: # df Filesystem Size Used Avail Use% Mounted on /dev/hdc1 5.
I have a strange problem. Recently, I started getting strange errors saying that things could not be saved in my home directory, and quickly checked with df..
Here is what I get:
# df
Filesystem Size Used Avail Use% Mounted on
/dev/hdc1 5.8G 2.2G 3.4G 40% /
/dev/hdc6 31G 31G 0 100% /home
/dev/hdd1 19G 832M 17G 5% /var/www
hmm... so I have 31G used in the home partition...
This morning, I searched for whatever is taking up all of this space and found a 300MB log file, and deleted it (far from 31G, but it's a start) then df showed some free space.
this afternoon, it was back to full, so I decided to look further. I did used the du -h --max-depth=1 commmand from the root folder and got this:
# du -h --max-depth=1
142M ./home
20K ./mnt
152K ./dev
20M ./etc
460K ./tmp
...
...
Can anyone point me in the right direction on this problem?
Thanks,
Tim
Here is what I get:
# df
Filesystem Size Used Avail Use% Mounted on
/dev/hdc1 5.8G 2.2G 3.4G 40% /
/dev/hdc6 31G 31G 0 100% /home
/dev/hdd1 19G 832M 17G 5% /var/www
hmm... so I have 31G used in the home partition...
This morning, I searched for whatever is taking up all of this space and found a 300MB log file, and deleted it (far from 31G, but it's a start) then df showed some free space.
this afternoon, it was back to full, so I decided to look further. I did used the du -h --max-depth=1 commmand from the root folder and got this:
# du -h --max-depth=1
142M ./home
20K ./mnt
152K ./dev
20M ./etc
460K ./tmp
...
...
Can anyone point me in the right direction on this problem?
Thanks,
Tim
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Well, I seemed to have spoken too soon... I ran into more errors when trying to unmount, and decided to shut down and restart. upon restart, fsck ran, and found some inode error, fixed it, and all is good in the universe now...
I feel really bad that I fixed this myself by basically restarting the dang thing, I will have to start follwing my own advice on that subject from now on...
I feel really bad that I fixed this myself by basically restarting the dang thing, I will have to start follwing my own advice on that subject from now on...
