topic Re: root directory is 100% full? in Operating System - HP-UX

root directory is 100% full?

Peter Ko_2 — Sat, 11 Jul 2009 02:24:23 GMT

Can someone help how to safely delete some files off the root? i noticed it is 100% full although the NNM still appears unaffected by it. Below is my files on the root:
________________________________

# ls -ls
total 277808
0 -rw-r--r-- 1 root sys 0 Nov 1 2006 -f
48 -rw------- 1 root sys 16666 Jun 12 00:11 .ICEauthority
16 -rw------- 1 root sys 152 Jun 12 00:11 .TTauthority
0 -rw------- 1 root sys 0 Jun 12 00:11 .Xauthority
16 drwxr-xr-x 11 root sys 8192 Jun 12 00:11 .dt
16 -rwxr-xr-x 1 root sys 5451 Nov 18 2006 .dtprofile
0 drwxr-xr-x 4 root sys 96 Nov 8 2006 .java
0 drwx------ 3 root sys 96 Nov 1 2006 .mozilla
16 -rw-r--r-- 1 root sys 10 Nov 1 2006 .mozilla-license
0 -r--r--r-- 1 root sys 0 Nov 7 2006 .ovweb.conf
16 -rwxrwxrwx 1 bin bin 1407 Nov 6 2006 .profile
0 drwxr-xr-x 2 root sys 96 Dec 12 2006 .ssh
16 drwxr-xr-x 6 root sys 8192 Nov 1 2006 .sw
0 drwxr-xr-x 2 root sys 96 Jan 5 2007 .vnc
0 lr-xr-xr-t 1 root sys 8 Nov 1 2006 bin -> /usr/bin
0 drwxrwxrwx 2 root sys 96 Nov 1 2006 cdrom
277488 -rw------- 1 root root 142065664 May 26 12:28 core
16 dr-xr-xr-x 13 bin bin 8192 Jun 11 23:52 dev
16 dr-xr-xr-x 30 bin bin 8192 Jun 11 23:53 etc
16 drwxr-xr-x 8 root root 8192 Nov 16 2007 home
0 lr-xr-xr-t 1 root sys 8 Nov 1 2006 lib -> /usr/lib
0 drwxr-xr-x 2 root root 96 Nov 1 2006 lost+found
16 -rw-rw-rw- 1 root sys 180 Nov 1 2006 lvextend.sh
0 dr-xr-xr-x 1 root root 1 Jun 11 23:51 net
16 dr-xr-xr-x 66 bin bin 8192 Nov 1 2006 opt
16 dr-xr-xr-x 13 bin bin 8192 Nov 1 2006 sbin
0 drwxr-xr-x 3 root sys 96 Nov 21 2006 scripts
16 -rw-rw-rw- 1 root sys 23 Apr 27 2007 shutdown.sh
16 dr-xr-xr-x 7 bin bin 1024 Jun 11 23:50 stand
16 drwxrwxrwt 12 root root 8192 Jul 10 21:58 tmp
16 dr-xr-xr-x 23 bin bin 8192 Nov 18 2006 usr
16 dr-xr-xr-x 23 bin bin 8192 Nov 1 2006 var
# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 557056 557056 0 100% /
/dev/vg00/lvol1 298928 29456 239576 11% /stand
/dev/vg00/lvol8 4718592 1566056 3132128 33% /var
/dev/vg00/varOV 20480000 13109087 6910791 65% /var/opt/OV
/dev/vg00/lvol7 3653632 1710832 1927648 47% /usr
/dev/vg00/lvol4 212992 16256 195264 8% /tmp
/dev/vg00/lvol6 3211264 2094552 1107992 65% /opt
/dev/vg00/OV 3080192 1066358 1888016 36% /opt/OV
/dev/vg00/lvol5 32768 27520 5248 84% /home
#

Re: root directory is 100% full?

Patrick Wallek — Sat, 11 Jul 2009 02:38:21 GMT

This file should be perfectly safe to delete, and it will free up approx 140MB.

277488 -rw------- 1 root root 142065664 May 26 12:28 core

Re: root directory is 100% full?

Dennis Handly — Sat, 11 Jul 2009 02:52:32 GMT

>Patrick: This file should be perfectly safe to delete

Right, that was easy. :-) You might want to use "file core" before you do, so you can track what application aborted.

If you keep getting them, you can do "mkdir core".

Re: root directory is 100% full?

Sajjad Sahir — Sat, 11 Jul 2009 06:24:06 GMT

Dear Friend

I am seeing one core file
277488 -rw------- 1 root root 142065664 May 26 12:28 core u can remove it
but before removing u should always check
the file type
by using the command file
file core

thanks and regards

Sajjad Sahir

Re: root directory is 100% full?

Sharma Sanjeev — Sat, 11 Jul 2009 06:36:17 GMT

Hi Peter

One core file is generated you can delete this.

277488 -rw------- 1 root root 142065664 May 26 12:28 core

Regards
Sanjeev

Re: root directory is 100% full?

SoorajCleris — Sat, 11 Jul 2009 06:40:56 GMT

Hi,

As our mates suggested you may remove the core file ( if it is a core file).

But investigate in to this, why the core file is existing there. It is recommended to have a differnt mount poing for this.

Regards,
Sooraj

Re: root directory is 100% full?

Duncan Edmonstone — Sat, 11 Jul 2009 07:55:58 GMT

of course its actually the root *filesystem* that's 100% full, not just the root directory. So to look for "large" files in the root filesystem you might try:

find / -size +10000000c -xdev -exec ll {} \;

that should show you files larger than 10MB (approximately)... of course you'd still need to figure out if you can actually delete any of those.

HTH

Duncan

Re: root directory is 100% full?

Johnson Punniyalingam — Sat, 11 Jul 2009 13:58:08 GMT

>>>But investigate in to this, why the core file is existing there. It is recommended to have a differnt mount poing for this<<

Yes, You are right

A core file is the result of an ordinary program aborting for any number of reason such as an unexpected signal, bad code, failed device, ... . A crash dump occurs when the kernel itself undergoes an unexpected event.

links, it should give better understanding of Core dumps and crash dumps,

http://docs.hp.com/en/J2237-90005/ch06s05.html
[Generating and Retrieving System Core Dumps]

http://en.wikipedia.org/wiki/Core_dump

http://www.unixguide.net/hp/hpuxcrashdump.shtml

Thanks,
Johnson

Re: root directory is 100% full?

Peter Ko_2 — Mon, 13 Jul 2009 14:14:04 GMT

Thank you everyone's help, i did a "rm core" and the root now is about 75%.

Re: root directory is 100% full?

Steven E. Protter — Mon, 13 Jul 2009 14:23:22 GMT

Shalom,

That is still a little high.

I would have moved the core file to a file system and taken a look at it there.

du -k | sort -rn | more

To find other biggies in root

SEP

Re: root directory is 100% full?

Mel Burslan — Mon, 13 Jul 2009 15:08:25 GMT

Considering you have half a gig worth space in "/" 75% full is not normal. Run this command to find any files larger than 1MB (roughly) and if you can not make sense out of them to decide which ones are safe to delete, post the output here to get further advice. If you encounter any core files in the listing 99.99% of the time, it is safe to delete those. Here is the command:

find / -xdev -size +1000000c | xargs ll | tee /tmp/largefiles.txt

this will display the file list on the screen while creating a copy of the list to file called /tmp/largefiles.txt for future use or editing.

Also, please assign points to the replies respective of how useful they are/were to you, solving your problem or enhancing your understanding of HP-UX.