Adding a new disk using SAM

[HSBC]

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.

[A. Clay Stephenson]

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.

[James R. Ferguson]

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...

[Steven E. Protter]

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

[HSBC]

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!

[HSBC]

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!

[Michael Tully]

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.

[Jeff Schussele]

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

[Michael Tully · Accepted solution]

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.

[Sandip Ghosh]

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