[SOLVED] Root partition full

MensaWater · 08-03-2012, 12:41 PM

Quote:

Originally Posted by ivanvodisek

Once I tried to delete "cache" directories in pursuit for a gig, but had to reinstall the whole system after.

Yep - two big dangers looking for space:
1) Not knowing what the file is - if you don't know what it is and can't find out do NOT delete it.
2) Not knowing whether the file is in use. You can run "lsof <filename>" to check if it is "open". If it is open do NOT delete it without first stopping the process(es) holding it open. (And again be sure you know what the processes are for before you stop them.)

aemtisup · 08-03-2012, 12:56 PM

@MensaWater:
# du -sxh /
4.9G /

# df -h /
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_dpgmsvm64-lv_root
50G 47G 189M 100% /

I don't get it... It doesn't make sense...

@acid_kewpie:
# du -xh --max-depth=1
4.0K ./media
0 ./net
16K ./lost+found
119M ./lib
0 ./selinux
4.0K ./opt
0 ./dev
4.1G ./usr
12K ./.dbus
544M ./var
0 ./proc
0 ./misc
20K ./mea
32K ./tmp
32M ./etc
4.0K ./srv
46M ./root
7.1M ./bin
4.0K ./mnt
4.0K ./home
0 ./sys
13M ./sbin
2.0K ./boot
4.9G .

acid_kewpie · 08-03-2012, 01:14 PM

Hmm, yes we're all baffled! and this persisted over a reboot right? So it's not an open file... erm...

aemtisup · 08-03-2012, 01:17 PM

yes, persisted after a reboot... I've got 3 other identical machines (same hardware, same software) and they all show around 5G of usage with df. I don't understand what's going on with this one... I assume du and df would get their info from the same place. Any chance one of them uses a file to store some data and that file could be corrupted thus giving false info?

suicidaleggroll · 08-03-2012, 01:20 PM

Quote:

Originally Posted by acid_kewpie

Hmm, yes we're all baffled!

I certainly know I am...

acid_kewpie · 08-03-2012, 01:20 PM

I would speculate about filesystem corruption. try fscking the root partition (from a rescue CD to be safest), maybe you'll end up with a large lump of not much in /lost+found to delete

ivanvodisek · 08-03-2012, 01:44 PM

not much help, but in ubuntu for few hundreds megs try:

Code:

sudo apt-get clean

aemtisup · 08-03-2012, 01:56 PM

@acid_kewpie: I'll try that Monday morning before the user gets in...

NyteOwl · 08-03-2012, 01:58 PM

My usual first suspects: accumulated log files, browser cache directories, archived e-mail, archived newsgroups.

MensaWater · 08-03-2012, 02:03 PM

Yep - at this point it looks like AcidKewpie is right. You'll need to do fsck on it. Make sure you have a good backup before proceeding.

acid_kewpie · 08-03-2012, 03:58 PM

Quote:

Originally Posted by aemtisup

@acid_kewpie: I'll try that Monday morning before the user gets in...

cool, let us know how it gets on, interesting case.

---------- Post added 03-08-12 at 09:58 PM ----------

Quote:

Originally Posted by NyteOwl

My usual first suspects: accumulated log files, browser cache directories, archived e-mail, archived newsgroups.

yes, but we moved on from that long ago.

---------- Post added 03-08-12 at 09:59 PM ----------

Quote:

Originally Posted by ivanvodisek

not much help, but in ubuntu for few hundreds megs try:

Code:

sudo apt-get clean

and the other unaccounted for 45gb?

aemtisup · 08-06-2012, 12:52 PM

Hmm.. Had to run a boot-up file system check (which found no errors) since I realized this morning that I'm unsure how to go about a fsck on the / partition... I found this link: https://unixbhaskar.wordpress.com/20...including-lvm/ somewhat helpful but I don't want to do something if I'm not sure about it... To complicate things, the root partition is a logical volume so I'm not sure I can use the basic procedure for creating the device... Anyone know if this procedure is correct (for LVM), or any other resource that could help me?

MensaWater · 08-06-2012, 03:22 PM

If you boot into single user mode it is typically safe to run fsck on your mounted / (whether its an LVM or not).

ivanvodisek · 08-06-2012, 03:48 PM

khm...

(if i didn't miss something, most of free space is unavailable and not reported). Too weird fsck couldn't fix this, U might loose some data. make backup.

i wander what gparted (like partition magic in win) would show? how about resize partition to min free space, then back to max free space? or convert it to ext2 then back to ext3? weird things happen here, maybe this would fix them and maybe i'm proposing a road to hell ]:-)

Wim Sturkenboom · 08-07-2012, 12:25 AM

Boot into single user mode
Unmount mounted partitions

Check with du

You may have data under the mount points /boot and/or /home due to a failed mount at some stage. 'du' will not see that; by unmounting, it becomes visible.

PS
please post any commands / results between [code] and [/code]