extending / and /stand

[Padraig Stafford]

I am at the beginning of my project to update from HP-UX 11.0 to HP-UX 11i v1.

I have been through the install document to compile my list of pre-requisites and have come up against a problem.

Most of the file-systems listed are below the minimum recommended values on my target servers. Most such as /var /opt /home etc I can solve reasonably easily.

The real stumbling blocks are / and /stand.

The production server has an AutoRaid attached with LUN's etc which adds another compilcation.

I have been reading the various threads on the issue and all seem to suggest ignite and adjust the file systems as part of the recovery.

I would like to avoid this if at all possible due to the risks and time needed.

There have been some mention of documents which describe a method using OnlineJFS (which caters for contigious disk space requirements etc) but I havent been able to find it.

Similarly one thread mentions a document KBRC00006582 but I can find a copy.

Has anybody extended / and /stand using a method other than ignite

[Rick Garland]

I found this document.
LVMKBRC00005108
Extending the root filesystem with OnLineJFS.

Need to have a another separate disk because these 2 filesystems have to remain contigious.

[Pete Randall]

You can also accomplish this by decreasing your swap area and utilizing the space gained for expansion. Frankly, the Ignite approach sounds much better to me. An even better approach would be to cold install onto another disk!


Pete

[Rick Garland]

I would agree with Pete.

This does not appear to be a straightforward task. 1st choice is the Ignite. 2nd choice is a fresh install onto other disk(s)

[Mel Burslan]

I second Pete's opinion. reducing swap to gain expansion space for / and /stand has been tested successful under certain circumstances but, since you are going to have the system unavailable, might as well use this chance to do it properly with ignite instead of hacking your way with swap shrinking.

[Torsten.]

Hi Padraig,

if a cold install isn't possible, I would recommend the ignite procedure. Make a backup of your system and boot from that tape. Select the interactive mode and configure your values. Be aware, use VT100 terminal emulation when working with ignite install!

[DCE]

To be redundant, I agree with Pete. This can be a real bear, and cause you lots of problems. A clean install on a spare disk will give you what you want. You can even mirror back to the original disk(s) if you want, and remove the "temporary" disk

[Cem Tugrul]

Hi,

Last year i had been updated my N-Class
server 11.00-->11i with Hp support engineer
using ignite without any problems...
to avoid any possible problems you have to
take healty backups also another important point patches-bundles must be ready for
your 11i

and an attachment may guide you...

Good Luck,

[Sandman!]

I have tried only the Ignite-UX approach.

cheers!

[Padraig Stafford]

The only thing that is putting me off of the ignite to a new disk option is the presence of the AutoRaid. We dont have LUNs rather than disks. I have never had to ignite the server with the AutoRaid and am a bit nervous that it might impact on the data LUNs which hold the Oracle File-Systems.

[Padraig Stafford]

One possibility is using the internal disk we have installed for disasters (normally the server boots of a LUN on the AutoRaid)

Perhaps I should install 11i on the internal disk and boot from it for a period of time while reconfiguring the LUN on the autoraid currently used for / /stand etc.

[Steven E. Protter]

The root filesystem must be contiguous.

The only real way to end up with a bigger one is to do the ignite backup and reinstall.

I've done it a number of times and its not as challenging as it sounds.

You can get some space back the way Pete says by reducing or removing the next filesystem on the disk.

pvdisplay -v /dev/dsk/root_disk

replace root_disk with a real disk.

The problem with this methodology is if it swap that you are removing you will be a short time without swap and your system could halt and fail to restart.

Your issue is what Ignite was designed to help you solve.

SEP

[Pete Randall]

Padraig,

I would definitely go with the internal disk. This way you can boot off the AutoRaid to fall back if you have issues. Once you're comfortable with the new install you could use MirrorDisk to migrate it to the AutoRaid if you really prefer to have it there. Personally, I prefer to use mirrored internal disks.


Pete

[Padraig Stafford]

Following the advice given in this thread I am leaning towards an Ignite recovery.

I have read about rebuilding non-vg00 file-systems using vgimport and map-files. Has anybody done this in an AutoRaid environment and was it easy/successful.

I would be more comfortable doing this in a discrete disk set-up. I am a bit nervous trying it on the AutoRaid.

[A. Clay Stephenson]

The AutoRAID itself is not a problem but you will not have the software you need to administer the array initially. The "trick" is to create the LUN's you need before doing the Ignite. Once created, the host computer doesn't need any additional software. I would create the LUN's that will comprise vg00 before doing the Ignite. Having said all this, I never house vg00 on any kind of array but always use simple disks.

[Leif Halvarsson_2]

Hi,
I have never used the Autoraid box but regulary used Ignite on other external Raid systems (including SAN arrays). From Ignites point of view, internal er external disks, Raid or simple disks is no difference.