Increasing file size on /

[Dimitri Karagiannis]

i'm installing some patches and my / filesystem is going to exceed it's limit. I've freed up as much as I could but I'm still going to need to extend it's size. I was just wondering what the right way of going about it is...
Much appreciated,

Dimitri

[Rick Garland]

Look into Ignite

It is a product on the Application CDs and does not require a codeword.

[Tommy Brown]

Even though it is available on CD, It would be far better to download it from the SW Depot. The latest is greatest.
Tommy

[Tommy Brown]

Sorry, Here is the link:
http://www.software.hp.com/products/IUX/index.html
Tommy

[Venu_2]

Hi,

It is bit difficult to increase the size of the root filesystem dynamically.

Reason is root should be contigous. If there is no other filesystem created after root in the root disk you can do the following way.

reboot the system in maintanance mode.

ISL> hpux -lm

# lvextend -L XXX /dev/vg00/rroot

XXX - new capacity of the filesystem.

# extendfs /dev/vg00/rroot

# fsck /dev/vg00/rroot

# lvlnboot -b /dev/vg00/stand

# lvlnboot -r /dev/vg00/root

# lvlnboot -s /dev/vg00/swap

# lvlnboot -d /dev/vg00/swap

# lvlnboot -R

# reboot

Hope this can help you

regards

venu

[John Palmer]

Do you really have to extend /? If you are patching, am I right in assuming that /stand is not a separate filesystem?
If so, you might find that you can get away with removing your previous kernel file (or moving somewhere else if you are ultra cautious) (/stand/vmunix.prev) as this gets overwritten anyway.
When generating a new kernel, the patching process needs enough room (temporarily) for three copies of the kernel (new, current and previous) it then moves new to current and current to previous so you end up with two copies.
Simply removing /stand/vmunix.prev before swinstall is a lot simpler than creating a whole new boot disk!

[Dimitri Karagiannis]

Thanks guys..

Much Appreciated
Dimitri

[Thomas G. Tudrej]

Hi,

have you tried the "cleanup" utility for patches? It allows you to remove all old filesets that were patched if you do not plan to roll back to previous state.

[George C. Sievers · Accepted solution]

That was my first task 4 years ago as a programmer converted to system administrator for a company with 10 HPUX 10.01 systems. The HP manuals outlined a procedure that was rather complex but it boils down to the following (if I remember correctly):

1. Make a new logical volume of the desired size making sure you follow the directions for creating a bootable volume.
2. Make that logical volume an alternate boot volume.
3. Copy all of your current root volume over to the newly created root volume.
4. reboot and interact with the IPL telling it to boot off the alternate boot lv.
5. remove the original root volume (lvrmboot).
6. make sure the new boot volume shows up as the only boot volume.
7. try rebooting on the new logical volume.

I'm not sure that coming up in maintenance mode will work. (Although I would be happy to be corrected in this.) Even in maintenance mode it would seem that the root lv would have to be mounted. A mounted lv can be extended but the filesystem on it cannot. Basically you have to find a way to unmount the root lv in order to extend it. The same problem holds true with other "busy" logical volumes such as /var /opt /tmp /home & etc. but they are much easier to deal with by manipulating the /etc/fstab.

[Dave Wherry]

The easiest way, and quite safe, is to use make_recovery. As stated earlier get the latest Ignite bundle.

make_recovery -AvC
This will create a tape using /dev/rmt/0m
If your DAT drive is not 0m use:
make_recovery -AvCd /dev/rmt/1m
fill in the correct device number.

Reboot your system and interupt the boot. Boot from the tape device. Do not use the automatic recovery. Go into interactive and you will be able to work through several screens where you can resize your logical volumes. Give them new values as needed and then let it go. It will reload everything and your system will be back as it was, with the changes you gave it.
I've done it several times and it works very well.