topic Re: Problem with lvextend in Operating System - HP-UX

Problem with lvextend

rleon — Mon, 20 Oct 2008 14:32:01 GMT

i have done a search on this issue but I have not found a previous answer that helps me.

# lvextend -L 900000 /dev/oraqunarc_vg/oraQUNARC1P02_lv
lvextend: Not enough free physical extents available.
Logical volume "/dev/oraqunarc_vg/oraQUNARC1P02_lv" could not be extended.
Failure possibly caused by PVG-Strict or Distributed allocation policies.

I have enough free space
# vgdisplay oraqunarc_vg
--- Volume groups ---
VG Name /dev/oraqunarc_vg
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 4
Open LV 4
Max PV 128
Cur PV 62
Act PV 62
Max PE per PV 4400
VGDA 124
PE Size (Mbytes) 16
Total PE 133734
Alloc PE 63751
Free PE 69983
Total PVG 8
Total Spare PVs 0
Total Spare PVs in use 0

There are no mirrored LV's

Re: Problem with lvextend

rleon — Mon, 20 Oct 2008 14:41:22 GMT

This problem is not with all LV's just two of them. They all have pvgs but I can extend the other ones just fine.

Re: Problem with lvextend

Tim Nelson — Mon, 20 Oct 2008 14:47:43 GMT

Please post the first page or two of lvdisplay -v /dev/oraqunarc_vg/oraQUNARC1P02_lv

Re: Problem with lvextend

rleon — Mon, 20 Oct 2008 14:55:57 GMT

# lvdisplay -v /dev/oraqunarc_vg/oraQUNARC1P02_lv | more
--- Logical volumes ---
LV Name /dev/oraqunarc_vg/oraQUNARC1P02_lv
VG Name /dev/oraqunarc_vg
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 400000
Current LE 25000
Allocated PE 25000
Stripes 0
Stripe Size (Kbytes) 0
Bad block NONE
Allocation PVG-strict/distributed
IO Timeout (Seconds) default

--- Distribution of logical volume ---
PV Name LE on PV PE on PV
/dev/dsk/c36t7d5 805 805
/dev/dsk/c36t7d6 805 805
/dev/dsk/c36t7d7 804 804
/dev/dsk/c36t8d0 805 805
/dev/dsk/c36t8d5 71 71
/dev/dsk/c36t8d6 71 71
/dev/dsk/c36t8d7 71 71
/dev/dsk/c36t9d0 71 71
/dev/dsk/c36t9d1 2157 2157
/dev/dsk/c36t9d2 2157 2157
/dev/dsk/c36t9d3 2157 2157
/dev/dsk/c36t9d4 2157 2157
/dev/dsk/c36t9d5 2157 2157
/dev/dsk/c36t9d6 2157 2157
/dev/dsk/c36t9d7 2157 2157
/dev/dsk/c36t10d0 2157 2157
/dev/dsk/c36t10d1 1061 1061
/dev/dsk/c36t10d2 1060 1060
/dev/dsk/c36t10d3 1060 1060
/dev/dsk/c36t10d4 1060 1060

--- Logical extents ---
LE PV1 PE1 Status 1
00000 /dev/dsk/c36t7d5 00162 current
00001 /dev/dsk/c36t7d6 00162 current
00002 /dev/dsk/c36t7d7 00162 current
00003 /dev/dsk/c36t8d0 00161 current
00004 /dev/dsk/c36t7d5 00163 current
00005 /dev/dsk/c36t7d6 00163 current
00006 /dev/dsk/c36t7d7 00163 current
00007 /dev/dsk/c36t8d0 00162 current
00008 /dev/dsk/c36t7d5 00164 current
00009 /dev/dsk/c36t7d6 00164 current
00010 /dev/dsk/c36t7d7 00164 current
00011 /dev/dsk/c36t8d0 00163 current
00012 /dev/dsk/c36t7d5 00165 current
00013 /dev/dsk/c36t7d6 00165 current
00014 /dev/dsk/c36t7d7 00165 current
00015 /dev/dsk/c36t8d0 00164 current

Re: Problem with lvextend

Torsten. — Mon, 20 Oct 2008 15:12:11 GMT

Do you have this file?

/etc/lvmpvg

Re: Problem with lvextend

Andres_13 — Mon, 20 Oct 2008 15:15:39 GMT

I think this is because the distributed allocation policy. You need add more space to your volume group in order to met your policies requiriments.

Have all the disks within this volume group the same size?

Regards!

Re: Problem with lvextend

rleon — Mon, 20 Oct 2008 17:08:45 GMT

VG /dev/oraqunarc_vg
PVG pvgorarca
/dev/dsk/c36t7d5
/dev/dsk/c36t7d6
/dev/dsk/c36t7d7
/dev/dsk/c36t8d0
PVG pvgorarcb
/dev/dsk/c36t8d1
/dev/dsk/c36t8d2
/dev/dsk/c36t8d3
/dev/dsk/c36t8d4
PVG pvgorarcc
/dev/dsk/c36t8d5
/dev/dsk/c36t8d6
/dev/dsk/c36t8d7
/dev/dsk/c36t9d0
PVG pvgorarcd
/dev/dsk/c36t9d1
/dev/dsk/c36t9d2
/dev/dsk/c36t9d3
/dev/dsk/c36t9d4
PVG pvgorarce
/dev/dsk/c36t9d5
/dev/dsk/c36t9d6
/dev/dsk/c36t9d7
/dev/dsk/c36t10d0
PVG pvgorarcf
/dev/dsk/c36t10d1
/dev/dsk/c36t10d2
/dev/dsk/c36t10d3
/dev/dsk/c36t10d4
PVG pvgorarcg
/dev/dsk/c36t10d5
/dev/dsk/c36t10d6
/dev/dsk/c36t10d7
/dev/dsk/c36t11d0
PVG pvgorarch
/dev/dsk/c36t11d1
/dev/dsk/c36t11d2
/dev/dsk/c36t11d3
/dev/dsk/c36t11d4

Re: Problem with lvextend

Torsten. — Mon, 20 Oct 2008 17:18:22 GMT

According to this you need free space in each group of disks - vgdisplay -v will tell you about this free space.

Likely you don't have enough free space on all disks ...

Re: Problem with lvextend

rleon — Mon, 20 Oct 2008 17:22:32 GMT

# vgdisplay -v oraqunarc_vg | more
--- Volume groups ---
VG Name /dev/oraqunarc_vg
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 4
Open LV 4
Max PV 128
Cur PV 62
Act PV 62
Max PE per PV 4400
VGDA 124
PE Size (Mbytes) 16
Total PE 133734
Alloc PE 63751
Free PE 69983
Total PVG 8
Total Spare PVs 0
Total Spare PVs in use 0

Re: Problem with lvextend

Tim Nelson — Mon, 20 Oct 2008 17:23:21 GMT

If you wish to continue with our lv having its extents distributed over a number of disks then you need to add more disks each having equal amount of free space to fullfil your request.

If you do not care then turn off the strict distribution.

Re: Problem with lvextend

Torsten. — Mon, 20 Oct 2008 17:29:07 GMT

vgdisplay -v vg...

This part is important:

--- Physical volumes ---
PV Name /dev/disk/disk4_p2
PV Status available
Total PE 4228
Free PE 364 <======
Autoswitch On
Proactive Polling On

Re: Problem with lvextend

Torsten. — Mon, 20 Oct 2008 17:35:46 GMT

In your current config the system will use an extend from

PVG pvgorarca
then
PVG pvgorarcb
then
PVG pvgorarcc
...

and so on while lvextend.

If at least one of these groups does not have enough free space, the command will fail.

You probably need to add new LUNs (disks) to these groups ...

I noticed there are already 62 disks in this VG - so somebody planned this config carefully - do not destroy this environment!

Re: Problem with lvextend

rleon — Mon, 20 Oct 2008 17:45:20 GMT

I planned this config and do not want to mess it up. But I dont understand why I can not extend if I have the free PE

Total PE 133734

Re: Problem with lvextend

Torsten. — Mon, 20 Oct 2008 18:08:50 GMT

The total is meaningless as long as at least 1 single disk has not enough space.

Re: Problem with lvextend

shanmuhanandam — Tue, 21 Oct 2008 06:26:17 GMT

Please post the output of
#vgdisplay -v oraqunarc_vg
In your case the lv is stripped accross the pvgs. so if you have equal free space on the disks in pvg then only you can extend.