File system full

[Luca Frigatti]

Hi all!
I've the following question:
I check my HP-UX server (HP-UX version 10.20) and I note that the root file-system (/) is full (used 100%)
Is there any way to check this file-system and reduce the used-space??
I use the find command to search any core file in the server, but there's no-one.

Thanks in advance for your help anche your support.
Regards,
Luca

[Martin Johnson]

"cd /; du -kx | sort -rn | more" will show you the directories using the most space. Check those directories to see what you can delete.

HTH
Marty

[Ron Bromwell]

Luca,
I think the first step would be to find out what is "filling-up" the root directory. Do an ll and pipe it to pg. Check the date field to find what was modified recently. Before removing anything, make sure it will not impact the machine in a harsh manner.

Ron

[Christopher McCray_1]

Hello,

This has been discussed several times; check out:

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x311eeea29889d611abdb0090277a778c,00.html

or

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x72ba3a7b3682d611abdb0090277a778c,00.html

or several others by searching these forums. I used "root full" in my search

Good luck

Chris

[Stefan Farrelly]

Check the sizes of;
du -s /etc /dev

/etc should be around 20-28Mb
/dev should be around 40k (not even 1 Mb!)

If yours are much larger then this is where to look for files which shouldnt be there which you can delete.

[Sajid_1]

The first thing I would check is the files in /dev. If somebody accidently gave 'om' instead of '0m' while taking a backup (/dev/rmt/0m), that will cause this issue. Check each directory in the root with:
# du -k
Check which directory holds the large space and find the culprit. You can try moving some files from some directories too. If you want to find the new files created in the system:
# find / -xdev -type f -mtime -2 -exec ll \;

this will list all files created within last 2 days.

[Jeff Schussele]

Hi Luca,

To determine the big files do the following
du -akx | sort -nr | more
This will sort, largest on down & restrict to only the / FS.

HTH,
Jeff

[Bill McNAMARA_1]

it is most likely that a device file was incorrectly named. Under /dev/ you'll probably have one enormous file.

find . * -size +50000 | xargs ll

Later,
Bill

[Hai Nguyen_1]

Luca,

You can try to search for files which are greater than 10MB in size and have a time stamp later than yesterday.
As root, perform the sequence:

# touch -t 0207312359 /tmp/time.txt
# find / -type f -size +20480 -newer /tmp/time.txt > /tmp/bigfiles.txt

Then look into the file /tmp/bigfiles.txt to spot the file which fills up the root filesystem. This may lead you to identify an active process which has caused this as well.

Good luck.

Hai

[harry d brown jr]

Luca,

There is a feature in your profile that allows you to find previous Questions you have posted, which makes it easier to take care of this:

This member has assigned points to 4 of 87 responses to his/her questions.

http://forums.itrc.hp.com/cm/TopSolutions/1,,BR650308!1!questions,00.html

live free or die
harry

[Kelli Ward]

One more quick thing you might want to check is /var/adm/crash, if /var/is not mounted as a seperate LVM, you might be full of crash files.
Good luck,
Kel

[hslion]

Hi,

Most of all, You have to check the /dev filesystems.
I think that you did not correctly backup to tape device so the backup data is created to filename under /dev.
Therefore, you check as belows;
#du -s /dev

Have a good luck.

[John Payne_2]

Luca,

If all the above fails to gain you space, (barring Harry's post, of course.) then I would ask if you had any filesystems unmounted while users were on the system. If so, it is possible that something was written to in a mount point, and then the filesystem was mounted on top of that. i.e. You have a /data filesystem, and it was unmounted. With /data unmounted, anyone in /data is actually part of /. Then users filled /data full of junk, and you mounted the filesystem. Then the junk is still there, and you are unable to see it bacuase the filesystem has been mounted, but you are getting dinged for the space in /.

I have seen this several times on machines. The problem with fixing it is that you have to unmount the filesystem at look at the mount points to make sure they are empty. (I once found a very large very old tar file sitting under a filesystem.)

Hope it helps

John