How do I extend VG after I increase EVA LUN

[Sunya_1]

I have RX5670 with HP-UX 11.31 connecting to EVA3000 as VG01..

If I resize the virtualdisk present from EVA to RX5670 from 5GB to 10GB..

and I do ioscan . I can see the new disk size. But I can't use command vgextend..

What is the command to extend VG after I resize the LUN..??

I have ever do to present the second LUN and add it to VG. But In this time I want to try this way.. Are there any idea for this work around. Or is it imposible to perform by this method?..

Thank you so much..

[Robert-Jan Goossens · Accepted solution]

Hi Sunya,

Have a look at the vgmodify command.

http://docs.hp.com/en/5992-3385/ch03s04.html#admin.vgmodify2

Regards,
Robert-Jan

[Robert-Jan Goossens]

add on, this is a better document.

http://docs.hp.com/en/vgmodify/vgmodify_wp_modified_final.pdf

[sujit kumar singh]

hi


this is good that 11.31 is intelligent enuf to tale care and provode u with the vgmodify command to take care whwn a underlying LUN is increased in size , but to make things simpler why do not u assign a new LUN and add to the VG and do a further lvextend and/or lvcreate?

LVM use like that always helps u ...

anyway as u shall refer to the manpages of the vggmodify u can see that there are 2 new options that is -a "for Online operations" and -E "explicitly for the Dynamic Lun Expansion"





Regards
Sujit

[sujit kumar singh]

hi Sunya,

U can do an Online DLE for a VG that is when the VG is online and the I/O are taking place for the VG only if u have the Sep 2008 of 11.31.


Please gather the following informations before u are trying to do this ...

for the VG from the vgdisplay -v O/P note the following:

Max_PE_Per_PV
Allocated PE
Free PE
PE Size
Max PV
Act PV etc

(Remember that the value MAX_PE_per_PV is also configurable using the command combination of pvmove and vgmodify in 11.23 as well as 11.31)

Also the new size of the disk that u have increased the LUN to.

#diskinfo -v /dev/rdisk/disk41 say and this is the only disk in that VG say.


having all this information u can go ahead with the Online DLE for that VG.

#vgmodify -t

this will show the tabular form of the changes as suggested. Lets say as u have already increased the LUN just check and we assume that u r not going to change the MAX_PE_Per_PV now.

Also We assume that the MAX_PE_per_PV value as set for the VG is enough that it will take care of the new increased number of the PEs in the PV.

Do an Online DLE in the review mode only using the command::

#vgmodify -v -r -a -E

once satisfied with the results,

do the Actual Onlinr DLE using the command as :

#vgmodify -v -a -E


so u r done with the Online DLE.


can check that using the command:

#vgdisplay -v


now u can go on and do lvcreate, lvextend .




please refer to the vgmodify_White_papers for more details
http://docs.hp.com/en/vgmodify/vgmodify_wp_modified_final.pdf


and man pages of the command vgmodify



Regards
Sujit

[sujit kumar singh]

Hi Sunya,


for the posts that are made in response to ur questions please assign the points:



please visit the following thread ...
http://forums1.itrc.hp.com/service/forums/helptips.do?#33

this might lead u to better responses

regards
sujit

[Sunya_1]

HI All,

Thank for valued guide response.. Please give me a moment to study in VGMODIFY. And Then I might comeback for either success or question.

[Sunya_1]

Hi All,

Oh How busy I'm. Now I come back with result from the test machine before I'm going to do with customer machine..

This is my vgdisplay.
# vgdisplay -v vg5gb
--- Volume groups ---
VG Name /dev/vg5gb
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 1
Open LV 1
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 1279
VGDA 2
PE Size (Mbytes) 4
Total PE 1279
Alloc PE 1225
Free PE 54
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 1.0
VG Max Size 81856m
VG Max Extents 20464

--- Logical volumes ---
LV Name /dev/vg5gb/lv5gb
LV Status available/syncd
LV Size (Mbytes) 4900
Current LE 1225
Allocated PE 1225
Used PV 1


--- Physical volumes ---
PV Name /dev/dsk/c13t0d1
PV Name /dev/dsk/c15t0d1 Alternate Link
PV Status available
Total PE 1279
Free PE 54
Autoswitch On
Proactive Polling On




and after I apply vgmodify command. It seem like my VG is version 2.0 and can't use with this command..

# vgmodify -v -r -a -E vg5gb
Usage: vgmodify
[-e MaxPhysicalExtents]
[-p MaxPhysicalVolumes]
[-l MaxLogicalVolumes]
[-v]
[-n]
[-r]
[-B bootable]
VolumeGroupName [pv_path ...]

vgmodify -o
[-v]
[-r]
[-B bootable]
VolumeGroupName [pv_path ...]

vgmodify -t
[-v]
[-n]
[-B bootable]
VolumeGroupName [pv_path ...]

Note: This command is not allowed for volume group version 2.0 or higher.
"a": Illegal option.


How Could I extend VG for DLE.

http://docs.hp.com/en/lvm-v2/L2_whitepaper_8.pdf This does't said about DLE for VG 2.0.

[sujit kumar singh]

Hi Sunya,

as u can see in the vgdisplay O/P for the VG vg5gb u can well see that this is a Vesion 1.0 VG is it should support the Online DLE as also the MAN pages of vgmodify do suggest that the Inline DLE canbe done on the version 1.0 VGs.


but
as u can see this paper and onwards from the pages where ONline DLE ius mentioned that is from page 30 -43 u can see that is easliy done.
http://docs.hp.com/en/vgmodify/vgmodify_wp_modified_final.pdf

so there are few things that u might try :
1)try creating the VG as explicitly Vesion 1.0 VG by specifying that as -V 1.0 with the vgcreate command
and see by running ONline DLE.(But ur VG already is V1.0 VG!!!!)
#vgchange -a -E /dev/vg5gb


OFFLINE METHOD

also if u are not able to do this online i hopw u can try by doing this offline as u can take the vg offline that is deactivate this one and then try doing vgmodify to increase the MAX_PE_PER_PV , then use the normal methods of lvcreate or lvextend to use the new PEs on the PVs of the VG.



however this will be helpful to know what is the OS release and Version of 11.31 u r running , it will be better if u can put in the latest patch Bundles for the Release, that can be helpful.

please post also

#swlist -l bundle
#vgcfgrestore -l -v -n /dev/vg5gb
#diskinfo -v dev/rdsk/c13t0d1

this will help here to more closely find the reason out.

Please find this post also as this might also be helpful
http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1302868
and see the post of Duncan. though this mioght not be applicable to ur case.


Regards
Sujit

[Sunya_1]

What stranged thing is .. the message
"Note: This command is not allowed for volume group version 2.0 or higher.
"a": Illegal option."
This message is happen everytime for every try about the way for creating VG as follow..
-Use SMH UI - Crear VG with version1 but by reviewing command. SMH UI doesn't put the option "-V 1.0"
-Create VG manually by putting option "-V 1.0"

This is my another try..

# /usr/sbin/pvcreate /dev/rdsk/c13t0d1
Physical volume "/dev/rdsk/c13t0d1" has been successfully created.
# /usr/bin/mkdir -p -m u=rwx,g=rx,o=rx /dev/vg55
# /sbin/mknod /dev/vg55/group c 64 0x010000
# /usr/bin/chmod u=rw-,g=r,o=--- /dev/vg55/group
# /usr/sbin/vgcreate -V 1.0 -A y -x y -l 255 -p 16 -s 1 /dev/vg55 /dev/dsk/c13t0d1 /dev/dsk/c15t0d1 <
Increased the number of physical extents per physical volume to 5119.
Volume group "/dev/vg55" has been successfully created.
Volume Group configuration for /dev/vg55 has been saved in /etc/lvmconf/vg55.cof
#
#
# vgdisplay vg55
--- Volume groups ---
VG Name /dev/vg55
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 0
Open LV 0
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 5119
VGDA 2
PE Size (Mbytes) 1
Total PE 5118
Alloc PE 0
Free PE 5118
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 1.0
VG Max Size 81904m
VG Max Extents 81904

Then I add lv(lv55) and new VxFS with mount /55 by SMH UI. and then I try vgmodify..


# vgmodify -v -r -a -E vg55
Usage: vgmodify
[-e MaxPhysicalExtents]
[-p MaxPhysicalVolumes]
[-l MaxLogicalVolumes]
[-v]
[-n]
[-r]
[-B bootable]
VolumeGroupName [pv_path ...]

vgmodify -o
[-v]
[-r]
[-B bootable]
VolumeGroupName [pv_path ...]

vgmodify -t
[-v]
[-n]
[-B bootable]
VolumeGroupName [pv_path ...]

Note: This command is not allowed for volume group version 2.0 or higher.
"a": Illegal option.

Sujit.. Attach files. are for your request..(#swlist -l bundle , #vgcfgrestore -l -v -n /dev/vg5gb , #diskinfo -v dev/rdsk/c13t0d1)

[sujit kumar singh]

Hi Sunya,


there are two ways check to this:
1) the support issue of EVA3k and eva5K with 11.31.
please look at the following thread
Also need to look at the following thread that says that EVA3000 and EVA5000 issues with 11.31
http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1232810426116+28353475&threadId=1129095

2) and the support of the -a option with the vgmodify command on ur system.

ur system says that "-a" option is illegal !!!!
can u simply give the coammand as
#vgmodify and show the O/P, this shud tally with the following

# vgmodify
Usage:
For deactivated version 1.0 volume groups,
vgmodify
[-e MaxPhysicalExtents]
[-p MaxPhysicalVolumes]
[-l MaxLogicalVolumes]
[-v]
[-n]
[-r]
[-B bootable]
VolumeGroupName [pv_path ...]

vgmodify -o
[-v]
[-r]
[-B bootable]
VolumeGroupName [pv_path ...]

For activated version 1.0 volume groups,
vgmodify -a -E
[-v]
[-r]
VolumeGroupName [pv_path ...]

To display a table of optimized possible volume group settings for an activated or deactivated version 1.0 volume group,
vgmodify -t
[-v]
[-n]
[-B bootable]
VolumeGroupName [pv_path ...]


Mark the Line "FOR ACTIVATED VERSION 1.0 VOLUME GROUPS"



also here is the O/P of the suggested command for DLE.
the root VG on my system is vgroot and i am trying that command in here.


# vgmodify -v -r -a -E vgroot
Volume Group configuration for /dev/vgroot has been saved in /etc/lvmconf/vgroot.conf
An update to the Volume Group is NOT required
Review complete. Volume group not modified
# vgmodify -v -a -E vgroot
Volume Group configuration for /dev/vgroot has been saved in /etc/lvmconf/vgroot.conf
An update to the Volume Group is NOT required
#



also from ur system i can find out that

HPUX11i-OE-Ent B.11.31.0803 HP-UX Enterprise Operating Environment --- BASE EOE of MAR 2008
HWEnable11i B.11.31.0803.318a Hardware Enablement Patches for HP-UX --- 0803 means MAR 2008
FEATURE11i B.11.31.0809.326a Feature Enablement Patches for HP-UX -- MAR 2008
QPKBASE B.11.31.0803.318a Base Quality Pack Bundle for HP-UX 11 --- MAR 2008



what i shall suggest is to get ur system running on these latest patch bundles "always a good practice so that u have the latest Enhancements"
this the O/P from my system


DETAILS ABOUT MY SYSTEM:
I am on 11.31 running on rx2600 (VSE OE Sept 2008 u can find in #swlist | grep -i oe)

# model
ia64 hp server rx2600

and
FEATURE11i B.11.31.0809.326a Feature Enablement Patches for HP-UX 11i v3, September 2008
HWEnable11i B.11.31.0809.326a Hardware Enablement Patches for HP-UX 11i v3, September 2008
QPKBASE B.11.31.0809.326 Base Quality Pack Bundle for HP-UX 11i v3, September 2008
HPUX11i-VSE-OE B.11.31.0809 HP-UX Virtual Server Operating Environment --- this is of Sept 2008

So i have all Feature11i, HWEnable11i and QPKBASE that of Sept 2008.

i would suggest u to get ur system have the latest patch bundles for Featur11i, HWEnable11i, and QPKBASE

3)can u try this expansion using the Offline MEthod of vgmodify?


REgards
Sujit