Fail lvextend

[Lorayne]

Hi

I have an EVA8000 and I am going to extend a Logical Volume to mirror on a Server rp4440. I have the follow problem:

# vgextend /dev/vg35 /dev/dsk/c9t4d1
vgextend: Warning: Max_PE_per_PV for the volume group (2347) too small for this PV (5887).
Using only 2347 PEs from this physical volume.
Current path "/dev/dsk/c6t8d1" is an alternate link, skip.
Current path "/dev/dsk/c6t8d2" is an alternate link, skip.
Volume group "/dev/vg35" has been successfully extended.
Volume Group configuration for /dev/vg35 has been saved in /etc/lvmconf/vg35.conf

# lvextend -m 1 /dev/vg35/histsicritc /dev/dsk/c9t4d1
lvextend: Not enough free physical extents available.
Logical volume "/dev/vg35/histsicritc" could not be extended.
Failure possibly caused by strict allocation policy


Can you help me...?''

Thanks,,,

[A. Clay Stephenson · Accepted solution]

The vgextend failed for exactly the reason cited. The maximum number of PE's per physical volume is set when the VG is created and cannot be increased. You will thus lose some space on this volume.

The lvextend failed because while you may have enough free extents in the VG as a whole there are not enough free extents to allow the mirrors to be allocated on separate PV's. You probably need to create still another LUN and add it to the VG.

[DCE]

aditionally, The max PE parameter is set at vg creation. You will need to destroy the vg and recreate it with a larger value in order to fully utilize the disk.

[Gary Cantwell]

Hi Lorayne,

Please take a moment to assign points to those who have taken the time to assist you, here's how:

http://forums1.itrc.hp.com/service/forums/bizsupport/helptips.do?#33

Thanks,

Gary

[Coolmar]

Yes, as DCE said you will have to destroy the entire volume group and then re-create it (increasing the max PE value) and all the lvms within in and then restore the data. It can be a pain, but it is what you have to do and there really is no way around it.

[Lorayne]

Hi

Thanks for all..