1834484 Members
3992 Online
110067 Solutions
New Discussion

lvm misery

 
Terrence
Regular Advisor

lvm misery

I just bound a lun consisting of three disks in raid 5 on an FC60 using this command.
amcfg -L A:6 -d 4:2,5:3,6:2 -r 5 -s 4 -force 000600A0B8093C62
I did a pvcreate and then a vgextend to add it to a volume group that already existed with two other luns of three disks each. All three should be identical.
I then used lvextend and fsadm to expand an existing logical volume.
This leaves me with a volume group displaying the following:
#vgdisplay lawdev
--- Volume groups ---
VG Name /dev/lawdev
VG Write Access read/write
VG Status available, exclusive
Max LV 255
Cur LV 4
Open LV 4
Max PV 16
Cur PV 3
Act PV 3
Max PE per PV 25000
VGDA 6
PE Size (Mbytes) 4
Total PE 25983
Alloc PE 19250
Free PE 6733
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

I want to add 18 Gigs to another logical volume , but it reports:
lvextend: Not enough free physical extents available.
Logical volume "/dev/lawdev/d02" could not be extended.
lvextend: Couldn't retrieve the list of the physical volumes
belonging to volume group "/dev/lawdev".
Failure possibly caused by strict allocation policy

I can't turn off strict allocation because it's striped.
Any ideas on how I use 18 Gigs of that free space?
7 REPLIES 7
RAC_1
Honored Contributor

Re: lvm misery

lvdisplay "that_lvol"

Anil
There is no substitute to HARDWORK
Terrence
Regular Advisor

Re: lvm misery

#lvdisplay /dev/lawdev/d02
--- Logical volumes ---
LV Name /dev/lawdev/d02
VG Name /dev/lawdev
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule striped
LV Size (Mbytes) 18000
Current LE 4500
Allocated PE 4500
Stripes 2
Stripe Size (Kbytes) 4
Bad block on
Allocation strict
IO Timeout (Seconds) default
RAC_1
Honored Contributor

Re: lvm misery

vgdisplay -v /dev/vgxx, Does it show pvs you added??
There is no substitute to HARDWORK
Terrence
Regular Advisor

Re: lvm misery

c4t0d6 is the new lun. It doesn't display the alternate path because the other controller is currently hosed. (I got a downtime coming up to replace it)

#vgdisplay -v lawdev
--- Volume groups ---
VG Name /dev/lawdev
VG Write Access read/write
VG Status available, exclusive
Max LV 255
Cur LV 4
Open LV 4
Max PV 16
Cur PV 3
Act PV 3
Max PE per PV 25000
VGDA 6
PE Size (Mbytes) 4
Total PE 25983
Alloc PE 19250
Free PE 6733
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/lawdev/lawdev
LV Status available/syncd
LV Size (Mbytes) 11000
Current LE 2750
Allocated PE 2750
Used PV 2

LV Name /dev/lawdev/d01
LV Status available/syncd
LV Size (Mbytes) 36000
Current LE 9000
Allocated PE 9000
Used PV 3

LV Name /dev/lawdev/d02
LV Status available/syncd
LV Size (Mbytes) 18000
Current LE 4500
Allocated PE 4500
Used PV 2

LV Name /dev/lawdev/lawtest81
LV Status available/syncd
LV Size (Mbytes) 12000
Current LE 3000
Allocated PE 3000
Used PV 2


--- Physical volumes ---
PV Name /dev/dsk/c6t0d2
PV Name /dev/dsk/c4t0d2 Alternate Link
PV Status available
Total PE 8661
Free PE 0
Autoswitch On

PV Name /dev/dsk/c4t0d3
PV Name /dev/dsk/c6t0d3 Alternate Link
PV Status available
Total PE 8661
Free PE 322
Autoswitch On

PV Name /dev/dsk/c4t0d6
PV Status available
Total PE 8661
Free PE 6411
Autoswitch On
RAC_1
Honored Contributor

Re: lvm misery

lvextend -L "new_sizeM" /dev/vgxx /dev/dsk/c4t0d6

What does it give??
There is no substitute to HARDWORK
Terrence
Regular Advisor

Re: lvm misery

#lvextend -L 36000 /dev/lawdev/d02 /dev/dsk/c4t0d6
Need more PVs for "2" Stripes. Only have "1" PVs.
Failure possibly caused by strict allocation policy
RAC_1
Honored Contributor

Re: lvm misery

Your LV was created with -i and -I options. man lvcreate for details.

See lvdisplay output.
Stripes 2
Stripe Size (Kbytes) 4

You will have to add two pvs to extend the LV.

Anil
There is no substitute to HARDWORK