topic Re: Adding a new disk using SAM in Operating System - HP-UX

Adding a new disk using SAM

HSBC — Tue, 11 Mar 2003 20:40:42 GMT

Hello.

I just installed a new 9.1 LVD scsi disk on an old E25/9000, booted and the disk is there recognized thru an ??ioscan -fnC disk??. SAM also recognizes it and I tried to extend all filesystems using the ??merged?? space from the new 9gb disk, but LVEXTEND is returning the following message (thru SAM):

Lvextend:
failure possibly caused by contiguous allocation policy
failure possibly causes by strict allocation policy.

The message is pretty clear, but is there a way to edit and change this policy or I??ll have to start from scratch?

Thanks for your support, these forums are very useful.

Jeffo.

Re: Adding a new disk using SAM

A. Clay Stephenson — Tue, 11 Mar 2003 20:46:10 GMT

The answer is probably no. Firstly, /, /stand, (and primary swap) must be contigious LVOL's so unless there is free space at the end of each of these (and that's very unlikely), they can't be extended. Secondly, if the LVOL's are mirrored there may not be enough room on separate disks (PV's) to allow both copies to be extended.

You should be able to extend /var, /home, /tmp, and /usr with little difficulty - especially if you also have OnlineJFS.

Re: Adding a new disk using SAM

James R. Ferguson — Tue, 11 Mar 2003 20:47:40 GMT

Hi:

'lvchange' offers the ability to modify either strict or contiguous allocation policies, but *with restrictions*. Consult the man pages for 'lvchange' for more information.

You don't indicate which volume group on which the logical volumes reside. IF it is vg00 (as I suspect), you are not going to (easily) be able to deal with 'lvol1', 'lvol2' or 'lvol3'.

Regards!

...JRF...

Re: Adding a new disk using SAM

Steven E. Protter — Tue, 11 Mar 2003 20:59:14 GMT

If you have mirror/ux, you could mirror those filesystems to the new disk, break the mirrors and reconfigure your system to boot off the new big disk.

mkboot /dev/dsk/c#t#d#

mkboot -a "hpux -lq (;0)/stand/vmunix" /dev/rdsk/c#t#d#

vgextend /dev/vg00/c#t#d#

lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c#t#d#
same for other logical volumes

lvlnboot -r /dev/vg00/lvol3
lvlnboot -s /dev/vg00/lvol2
lvlnboot -d /dev/vg00/lvol2
lvlnboot -b /dev/vg00/lvol1
lvlnboot -R
lvlnboot -v
setboot -a path_of_disk

reboot, interupt, change the primary path

The logical volumes above must be contiguous.

to successfully extend the filesystems above you'll need to modify these steps.

Actually they might not work..

New approach.

Make an Ignite tape. make_tape_recovery

boot box

interupt
sea

bo P# # is the number of the sequential tape device.

Interupt the Ignite process when prompted and you can within limits change the size of the filesystems as they are laid down.

I like idea two much better.

SEP

Re: Adding a new disk using SAM

HSBC — Tue, 11 Mar 2003 21:09:34 GMT

Fast response, thanks for all attention.

Well, yes, the VG in use is VG00 and I am almost satisfied if I be able to extend only the /home/usr/opt/var/tmp.

The disks aren??t mirrored. I got a 2gb + a 9Gb one.

So, I can assign the new disk to the VG00 (already done) and extend only the /home/usr/opt/var/tmp ??? )will try that tomorrow.

Thanks!

Re: Adding a new disk using SAM

HSBC — Tue, 11 Mar 2003 21:12:16 GMT

Hummm. Thanks for the FAST reply!

Yes, VG00 and NO mirroring.
Just a 2Gb + a 9Gb Hd.

So, you mean I can just (already) add the new disk to VG00 and extend ONLY /home/usr/opt/var/tmp without coming into trouble?

Extending only these filesystems would be a good answer for me also.

Will try that tommorrow.

Thanks!

Re: Adding a new disk using SAM

Michael Tully — Tue, 11 Mar 2003 21:16:59 GMT

If you've added a 9Gb disk to a VG that had only a 2Gb disk to begin with, your only going to get 2Gb of the 9Gb disk anyway. Unfortunately this is how LVM works. Once you've set up your VG with DISK A, any subsequesnt disk will only be seen as the same size or smaller.

Re: Adding a new disk using SAM

Jeff Schussele — Tue, 11 Mar 2003 21:23:21 GMT

Hi Jeffo,

Unfortunately Michael's correct. Chances are VERY, VERY high that when you extend vg00 with the new disk, you'll only be adding 2 Gb.
Do a
vgdisplay vg00
and note the Max PE per PV value. Multiply that be PE size (4 Mb by default) & that value will be the largest size that can be added to the VG by adding another disk.

Your best bet will be to create 2 Ignite tapes (to be safe) & use that tape to recreate vg00 on the 9Gb disk.
You could then extend that to 11 Gb if you desire because the values mentioned earlier will now be larger & the whole 2Gb can be used.

Rgds,
Jeff

Re: Adding a new disk using SAM

Michael Tully — Tue, 11 Mar 2003 21:34:51 GMT

I would create an ignite tape for the OS in interactive mode and place it onto the 9Gb drive. Once that is successful, you could utilise the 2Gb disk as a second disk.

To create the ignite tape:

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

You can get the latest ignite from here. It won't affect any of the rest of your OS.
http://www.software.hp.com/products/IUX/download.html

'vgreduce' the disk from VG before starting.

Re: Adding a new disk using SAM

Sandip Ghosh — Tue, 11 Mar 2003 22:09:30 GMT

Or other wise you can do as follows.

Take out the disk from vg00.
Create another vg with the new disk.
Create a new logical vol according to your requirement.
Mount it on a temp directory and copy the contents of that directory.
Delete the contents of the existing directory.
Mount the new filesystem at that specific directory.

Sandip

Re: Adding a new disk using SAM

HSBC — Wed, 12 Mar 2003 12:50:13 GMT

Hello!

I just downloaded ignite and was about to install it, but decided to check on the Schussele hints.
Running vgdisplay vg00 showed me the result below, that makes me think that IS possible adding a HD up to 10gb!? (2500 * 4?)

Please confirm that. How could I correctly try to extend the VG to that new HD without using SAM (or even using SAM also)?

Thanks!

--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 8
Open LV 8
Max PV 16
Cur PV 2
Act PV 2
Max PE per PV 2500
VGDA 4
PE Size (Mbytes) 4
Total PE 2677
Alloc PE 442
Free PE 2235
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

Re: Adding a new disk using SAM

HSBC — Thu, 13 Mar 2003 17:24:21 GMT

Allright, I am running make_tape_recovery right now. It complained about the LIF volume in var/tmp (space). The MAN saids it needs at least 32 Mb and there was 56 there. Weird. Well, specified the -B option to make it use the /tmp which has around 300Mb free.

My doubt is what the correct command line to restore the tape with make_recovery to the new HD? Any special options or just let the HD there (already VGreduced)?
How to proceed after the restore? Only a boot will do it?

thanks!