/ filesystem filling up

[Phil Davey]

N class running HP-UX 11.11
I have followed most of the advice in the different posts regarding root filesystem problems, but still have an issue because the lvol is just too small (only 140MB).

Question: Can I put /etc/vx into a separate lvol in a similar way to /etc/lvmtab? I can create a new lvol in vg00, so the question is really will the system still boot if I do this?

[Johnny Damtoft]

There is alot of options, for adding more space to the / filesystem.

The best way, and the recomended way is to create an IgniteUX Backup of the systemdisk, so you can do a complete restore from this backup.

At the beginning of the backup you should be able to change the sizes of the filesystems of your vg00 volumegroup. Here you just give "/" the amount of space you want.

I'm doing this via an Ignite-UX Server setup.


-- Johnny

[Peter Godron]

Phil,
if you have gone through the montpoint and have removed any un-needed files and still have problems, I would create an recovery tape , bring the machine to single user, resize and restore.

Long term that seems the best to me. Starting to move default locations is normally not a good idea !

[Sandy Chen]

Hi,

Best way to increase / filesystem is to backup/restore via Ignite. The simplest and the safest way according to me

Regards,
Sandy

[Bill Hassell]

/etc/vx can get very large with a large number of disks and lvols, but it must remain in the / (root) lvol. The reason is that in single user mode, only /stand and / are mounted. Post the size of your biggest / directories:

du -kx | sort -rn | head

The two largest directories are always /etc/ and /sbin. If you haven't move root's HOME out of /, that is a very important task. There should be *NO* ordinary files in / and no root user directories in / such as .elm or Mail.

[Phil Davey]

Thanks Bill. Here is the output you requested.
135256 .
89536 ./etc
63232 ./etc/vx
44192 ./sbin
32760 ./etc/vx/type
29440 ./etc/vx/static.d
28728 ./etc/vx/static.d/build
16720 ./etc/opt
14864 ./etc/vx/type/static
9976 ./etc/opt/resmon

There are some small ordinary files in there, but we are talking KB rather than MB.
I think I will have to convince the customer to let me have an outage to rebuild from Ignite.

[Sp4admin]

Hi Phil,

The best way would be to create a ignite tape and boot oof of that hen you can use menus to naviagte to the / file system and make you change. This will cause a reboot.

good luck!
sp,

[Tim Nelson]

One other place to look..

/dev/ should have few, if any, regular files.

find /dev -type f

I typically ran into this when a backup was executed and the output device name got mistyped and hence a file created in /dev vs it going to an actual device.

[Bill Hassell]

Phil wrote:

135256 .
89536 ./etc
63232 ./etc/vx
44192 ./sbin
32760 ./etc/vx/type
29440 ./etc/vx/static.d
28728 ./etc/vx/static.d/build
16720 ./etc/opt
14864 ./etc/vx/type/static
9976 ./etc/opt/resmon

These are normal values for a system with a large number of disk volumes. So this is indeed a case where 140 megs is a bit too small and will need a reinstall from Ignite to layout the lvols differently. Be sure to keep a paper copy vgdisplay -v vg00. Use this as a command:

make_tape_recovery -I -v -x inc_entire=vg00 -a /dev/rmt/whatever_mn

[Phil Davey]

I will arrange a rebuild with the customer.