/

[navin]

Is it possible to extend the / file system. if so can i handle as we do for other filesystems like /opt and so on.
appreciate your help.

[A. Clay Stephenson]

In a word, no. / must be housed in a contiguously allocated LVOL. The supported mechanism to expand the root filesystem is via an Ignite. You can shrink the size of primary swap and then use the additional space to extend / but this is an unsupported method. In any event, make sure you have a valid Ignite backup before even thinking about Plan B. Normally there is no need to extend / (unless you made it default size during the install) and now want to do an OS upgrade. In that case, consider it lesson learned and always make / and /stand a little biggger than default.

[DCE]

The best way to extend / is to make an ignite back up of the system, and perform an interactive ignite restore to the same system. This will allow to specify sizes for any and/or all of your lvol's. On line JFS, if you have it, is an option for other mount points.

Be sure to back up all of your data before attempting any of the above

[navin]

Thanks for the reply. is there any link that i can refer for a ignite restore procedure and inturn how to extend / in that process. Currently i have a tape for the system(make_tape_recovery).
thanks much

[DCE]

You can find the manual here

http://www.docs.hp.com/en/B2355-91049/index.html

[George Liu_4]

I may disagree the above posts. I have extended ROOT on several systems and haven't see any negative impacts. I have used vxfs and hfs on 10.20 and 11i

[KapilRaj]

I am not listing the exact procedure , but from what I remember you should be able to do the following.

No outage required , if you have online jfs. If you do not have online jfs , do all the following in LVM maintenance mode.

a. Login as root.
b. find out the next logical volume after lvol3(assumed lvol3 is root) ..
c. pvmove that logical volume onto the newly added disk [ pvmove -n lvol4 /dev/dsk/cXtXdX]
d. now you should be able to increase root filesystem to an additional `size_of_the_lvol4`.
e. pvmove the lvol4 back to root vg ( vg00)

Do the lvlnboot ... commands for boot,swap,dump and root lvols.

This should work , rather *will work. boot,swap and root are the only lvols that needs a contegeous policy. so , it does not matter where lvol4 is .

So what I did here is , moved lvol4 away from lvol3 , thus creating a contegeous space right after lvol3. If you need more space on "/" you will be able to move lvol5 ...6 to the next disk and do the stuff. Do remember to migrate them back to the original disk.

Now, if you have mirrored rootvg, then i would say break the mirror before you do this.

I would give it a try on a test box bwfore I do this myself. I don't have a machine infront of me so. So this is not a tested procedure. Please test it before you do on a prod box.

Regds,

Kaps

[KapilRaj]

A small correction. Add the following after Step "a".
====
a[1] . Find out a free disk / unmirror the rootvg and make that disk free.
====

[Geoff Wild]

Kaps step D should be:

pvmove -n /dev/vg00/lvol4 /dev/dsk/CURRENT /dev/dsk/NEW

Remember - pvmove only works in the existing volume group.

Rgds...Geoff

[KapilRaj]

thanks .. long time I hv not typed an hpux command .. it is the 'aix impact' you have seen. Yes, I understand pvmove works only in the same VG.

Regds,

Kaps