/ is full (100%)

[student_of_unix]

hi ,
can some one help me with this problem.

os: hpux B.11.11 U 9000/800

Problem: / is at 100%, pls let me know how to deal with this problem.
increaseing the size of / is not possible.


Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 245760 244728 1032 100% /

Regards
Ak

[Pete Randall]

First thing to do is look for core files:

find / -name core

Then check for mistakes in the /dev directory (usually caused by someone mistyping a device name: /dev/rmt/Omn instead of /dev/rmt/0mn, for example)

find /dev -type f


Pete

[Doug O'Leary]

find / -xdev -mtime -2 -print | \
xargs -i ls -ld {} | sort -n -k 5

That will display all the files that have been modified in the last 2 days sorted by filesize.

Examine the list, ID the largest that's *NOT* OS related and either delete it or move it.

Once you have / below 100%, ID what's getting added to the root filesystem and create a new filesystem for those files.

HTH;

Doug

[spex · Accepted solution]

Hello,

10 largest directories in the root filesystem:
$ du -kx / | sort -rn -k1 | head -n 10

10 largest files in the root filesystem:
$ find / -type f -xdev -print | xargs -e ll | sort -rn -k5 | head -n 10

Recently modified files in the root filesystem:
$ find / -type f -xdev -mtime -1 -print | xargs ll | sort -rn -k5

PCS

[Richard Hepworth]

Hi,

If increasing the filesystem is not an option you need to find out where your using space in the root filesystem and remove whatever possible. Given the size of your root filesystem I wouldn't say there is much you could remove.

Try

du -x / | sort -n

regards,

Richard

[Matti_Kurkela]

If you have large (on the order of a terabyte) VGs configured, you might have big VG configuration backup files in /etc/lvmconf directory.

Removing the VG configuration backups makes it more difficult to recover if you have VG problems, but a 100% full root filesystems is worse. As a compromise, you might move other VG configuration files to some other location, but keep only the vg00 configuration backups in that directory.

Remember that the LVM commands may generate configuration backups automatically, so make a habit of checking the free space on the root filesystem before and after making configuration changes to large VGs. You might also consider using the "-A n" option in the LVM commands to disable backup creation, then using "vgcfgbackup" manually to create the configuration backups to a place of your choice.

MK

[Bill Hassell]

A very common error is /dev has a large backup file in it. The typical name for the first tape drive is /dev/rmt/0m which is not the same as /dev/rmt/om. Most backup programs have no status checking concerning the tape drive so the om name becomes a backup stored in /dev which is the / filesystem. There must be *NO* ordinary files (like a backup) in /dev:

find /dev -type f -exec ll {} +

[bhargavi]

First check for the large files using
du -x | sort -rn.
After u found the files with larger sizes trim it if the file is unwanted or cleanup the file system as cleanup -c 2

[student_of_unix]

thanku everyone