Expanding /stand

[Mark Greene_1]

I'm am going to be expanding /stand on one of my L2000 running HP-UX11.0 in order to be able to apply the most recent Quality, Hardware, and Security patches. I am planning on using ingite to do the filesystem expansion.

My question is do I have to do the interactive restore do the expansion, or can I do a "preview" make_tape_recovery save and then make the modifications to the logical volume information in /var/opt/ignite/recovery/config.recover and then do the "resume" make_tape_recovery and then just restore from the tape?

thanks,
mark

[Pete Randall]

Good question, Mark - I don't know.

However, being the nervous, overly cautious type in cases like this, I would prefer to babysit every step of the interactive version anyway.

Pete

[Mark Greene_1]

Pete,

I've expanded non-OS critical volumes this way in the past by doing the prevew, increasing the size allocation, doing the resume to run the save, and then the reboot and restore.

Obviously with something as significant as /stand, I want to double check this!
mark

[Pete Randall]

Mark,

I'd just never thought of it. From reviewing the config file, it sure looks like it ought to work. I'll be interested to hear your results.

Good luck,
Pete

[Hai Nguyen_1]

Mark,

If I were you, I rather change the size of a logical volume interactively. Go with the other approach if you plan to ignite more than one box.

Hai

[Patrick Wallek · Accepted solution]

You could do it the way you are talking about Mark.

I like going through the interactive menu though so I KNOW what is happening.

I'm just curious though, why do you need to extend /stand in order to apply patches? Unless you are keeping several old kernels as backups, /stand should change significantly when you install patches.

[fg_1]

Mark,

Just my 2 cents, but if your 9% short, i would bump it up more than just the 10% your thinking about. The same thing could occur when you go to do the next rd of patches and updates. If disk is not an issue bump it up a little more. We here use 150MB as our /stand size.

Gl Frank G.

[Patrick Wallek]

Damn, it'd be nice if I could type.

My last statement above should read "/stand should NOT change significantly when you install patches".

[Mark Greene_1]

Patrick,

I need to make /stand about 10% larger than it is:

/dev/vg00/lvol1 83733 61841 13518 82% /stand

I tried loading the latest Quality patch and got the error message that /stand was about 9% to small.

There is a vmunix.prev in there I thought about removing, as well as a vmunix_test under /stand/build/ which I probably will remove prior to doing the save. But seeing how these will get recreated as a part of doing the patch upgrades, I'm really just delaying the problem.

mark

[James R. Ferguson]

Hi Mark:

If you have made your 'make_tape_recovery' recovery tape with the '-I' option:

# make_tape_recovery -x inc_entire=vg00 -I -v -a /dev/rmt/0mn

...then when you boot from the tape the recovery will be "interactive".

Boot from the tape; Respond "no" when asked if you want to interact with IPL. After about 10-minutes you will see "Recovery tape created from system on .". Press any key to continue.

From the Ignite menu, choose "Install HP-UX/Media Only". Select "Advanced Installation" and choose the "Filesystems" tab.

Choose your target disk and resize your filesystems to you tastes.

Regards!

...JRF...

[Martin Robinson]

I can see no reason why you can't just umount(1m) /stand and enlarge it using extendfs -F hfs. I have sometimes seen systems where /stand has got unmounted somehow. The symptom is that the kernel is then unreadable for commands like netstat.

Try fuser on your /stand partition!

Obviously *I* am not going to try this first! ;->

[Rory R Hammond]

Martin,

Interesting Idea. You are correct that fuser to stand's lvol has nothing attached to it. Remember, stand is contigous, and swap is right next to it. you would have to move lvols around by mirroring or moving, and after resizing put them back in disk order. (lvlnboot -R) etc. It would be fun to try on a development box. If it worked It still would not be worth doing on a production box and risk a error in procedures. Ignite is a well documented and does work. I still like the thought....

[Mark Greene_1]

Actually, if you search the hp site for "expand /stand", you'll find a 10.20 document that explains how to do it without using ignite. It is not for the faint of heart, as you have to remove swap and recreate it after you expand /stand, among other things.

If I have to get all the users off the system to get it to single usermode anyway, I'll take the ignite method!

mark

[Pramod_4]

If you can afford a system reboot and shrink your swap a little then you can extend your stand without re-igniting your box. I have personally used this method and it works successfully.

Following are the steps:

Reboot your system in LVM maintenance mode:

At the ISL prompt enter the following:

ISL> hpux ???lm

This will boot the system in LVM maintenance mode and you will see a ???#??? prompt.

Do the following at the ???#??? prompt:

# vgchange ???a y /dev/vg00

# lvremove /dev/vg00/lvol2 ( You are removing swap !)

extend your /stand logical volume now???.

# lvextend ???L 200 /dev/vg00/lvol1

Create your primary swap now??????

# lvcreate ???C y -r N -s y ???L (Original size ??? the size you grabbed for /stand lvol )-n lvol2 /dev/vg00

# Please note that size of lvol1 + lvol2 should not exceed 2GB.

# lvlnboot ???R ( This will update the BDRA with newly created swap and stand.)

# vgchange ???a n

# reboot

[Johnny Kwok]

Avoid using Pramod instructions:

He left out a few instructions (like extending the file system); If you follow exactly, the reboot would fail complaining not able to find vmunix or vmunix is not executable.

This is the thread to complete instructions to expand /stand,

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x56085ec05a7ad711abdc0090277a778c,00.html

[Mark Greene_1]

I used the ignite process to do it. It went fine, so I'll probably stick with that method, should I have to do this on another system.

mark