Increasing "root" (/) volume.

[Sergei Kazakov]

How I can to increase root volume? Sometimes system goes coredump procedure and filling all free disk space on root volume that cause inscorrect performing of shutdown or restart procedures.

[Cheryl Griffin]

First, you have to stay on top of general maintenance and routinely look for files that should not be there which can be removed. Use a cron job for instance to search for "core" files which are left behind by commands or applications. (Note: this does not mean files like "core.h", simply "core").

Next, keep /var/adm/crash clean. Get the crash analyzed and remove old crash files when the problem has been resolved.

Finally, if root was sized too small, there are two supported ways of increased root filesystem: cold install OR make_recovery (Ignite utility). Make a make_recovery of root, restore it to your system. During the restore you go into interactive mode and under the advanced options, you increase the size of the root filesystem. There have been many many posts in the forums how to do this.

To search forum messages: use the search tab from the left, use keywords like: root, make_recovery, etc. and click the box for forums.

Ignite's home is http://www.software.hp.com/products/IUX/

[Patrick Wallek]

Cheryl is correct in recommending the Ignite-UX solution for increasing the size of your / directory. A re-install froma make_recovery tape and a cold install of the OS are your only 2 options.

Another thing to check in your / directory to free up some space is to look and see if you have any large files in /dev/rmt/directory. People occasionally accidentally create a tar file called 'om' or 'Om' when the really mean to use the '0m' device.

[Ovidiu D. Raita]

You can avoid the need for a bigger root file systems if you configure you system correctly:
1. no user accounts reside in root (separate /home)
2. no user has rights to create files in root
3. set a cron job to remove the core dumps
4. have a separate fs for /usr/adm/crash
5. separate file systems for /stand /opt /var /usr ...
6. no application logs written to root

If you're missing any of these I'd advise you first to try to find a way to change the config.

Ovidiu

[Wodisch]

Hello Sergej,

if you have a spare disk that you can put into your root
VG, the add it there, "pvmove" all LVs which are
physically located after your root-LV to the new disk,
increase it on-line with "fsadm" and "pvmove" the
other LVs back to first disk. Then you can "vgreduce"
thar spare disk frm the root Vg.
Needed to to this are:
Advanced Journal File System installed
a spare disk with a physical size fitting into your
root-VG (and an empty "slot" in the root VG)
some space unallocated on the root disks
(or you move some LV to another physical
disk or even VG, candidates would be "/home"
and "/tmp" and "/var")

HTH,
Wodisch