lvextending strict/distributed Lvol

[jsk_cbe]

Hi, I am the hp-ux/storage administrator, in my new organisation the lvm has been configured in the following way:
eoerr3p@root:/> vgdisplay -v vgsap
--- Volume groups ---
VG Name /dev/vgsap
VG Write Access read/write
VG Status available, exclusive
Max LV 255
Cur LV 18
Open LV 18
Max PV 16
Cur PV 5
Act PV 5
Max PE per PV 12779
VGDA 10
PE Size (Mbytes) 8
Total PE 52393
Alloc PE 44749
Free PE 7644
Total PVG 1
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 1.0
VG Max Size 1635712m
VG Max Extents 204464

--- Logical volumes ---
LV Name /dev/vgsap/lvsapmnt
LV Status available/syncd
LV Size (Mbytes) 5120
Current LE 640
Allocated PE 640
Used PV 4

LV Name /dev/vgsap/lvsapr3p
LV Status available/syncd
LV Size (Mbytes) 10240
Current LE 1280
Allocated PE 1280
Used PV 4

LV Name /dev/vgsap/lvoracle
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 128
Allocated PE 128
Used PV 4

LV Name /dev/vgsap/lvoraclient
LV Status available/syncd
LV Size (Mbytes) 616
Current LE 77
Allocated PE 77
Used PV 4

LV Name /dev/vgsap/lvorastage
LV Status available/syncd
LV Size (Mbytes) 6144
Current LE 768
Allocated PE 768
Used PV 4

LV Name /dev/vgsap/lvorar3p
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 128
Allocated PE 128
Used PV 4

LV Name /dev/vgsap/lv102_64
LV Status available/syncd
LV Size (Mbytes) 6144
Current LE 768
Allocated PE 768
Used PV 4

LV Name /dev/vgsap/lvoraarch
LV Status available/syncd
LV Size (Mbytes) 25600
Current LE 3200
Allocated PE 3200
Used PV 4

LV Name /dev/vgsap/lvsapreorg
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 128
Allocated PE 128
Used PV 4

LV Name /dev/vgsap/lvsapdata1
LV Status available/syncd
LV Size (Mbytes) 71680
Current LE 8960
Allocated PE 8960
Used PV 4

LV Name /dev/vgsap/lvsapdata2
LV Status available/syncd
LV Size (Mbytes) 71680
Current LE 8960
Allocated PE 8960
Used PV 4

LV Name /dev/vgsap/lvsapdata3
LV Status available/syncd
LV Size (Mbytes) 71680
Current LE 8960
Allocated PE 8960
Used PV 4

LV Name /dev/vgsap/lvsapdata4
LV Status available/syncd
LV Size (Mbytes) 71680
Current LE 8960
Allocated PE 8960
Used PV 4

LV Name /dev/vgsap/lvoriglogA
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 128
Allocated PE 128
Used PV 1

LV Name /dev/vgsap/lvoriglogB
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 128
Allocated PE 128
Used PV 1

LV Name /dev/vgsap/lvmirrlogA
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 128
Allocated PE 128
Used PV 1

LV Name /dev/vgsap/lvmirrlogB
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 128
Allocated PE 128
Used PV 1

LV Name /dev/vgsap/lvSCS01
LV Status available/syncd
LV Size (Mbytes) 10240
Current LE 1280
Allocated PE 1280
Used PV 1


--- Physical volumes ---
PV Name /dev/disk/disk54
PV Status available
Total PE 12779
Free PE 759
Autoswitch On
Proactive Polling On

PV Name /dev/disk/disk55
PV Status available
Total PE 12779
Free PE 2040
Autoswitch On
Proactive Polling On

PV Name /dev/disk/disk56
PV Status available
Total PE 12779
Free PE 2040
Autoswitch On
Proactive Polling On

PV Name /dev/disk/disk57
PV Status available
Total PE 12779
Free PE 2040
Autoswitch On
Proactive Polling On

PV Name /dev/disk/disk58
PV Status available
Total PE 1277
Free PE 765
Autoswitch On
Proactive Polling On


--- Physical volume groups ---
PVG Name PVRAID5
PV Name /dev/disk/disk54
PV Name /dev/disk/disk55
PV Name /dev/disk/disk56
PV Name /dev/disk/disk57


eoerr3p@root:/>

The local HP engineers have done this way.
4 disks are allocated to a PVG group.
And there are 18 volumes created on that with different size.
Now i need to increase 4 of the lvols. but due to this strict allocated i cannot do it even though i have enough space in total, because its distributed.
If I allocate more disks(LUNS) and create another PVG can I extend a LVOL across 2 PVGs.?? or I need to allocate in same PVG..?
is this method strict/ distributed allocation for a NON-Mirrored volume is it really a good practice??????
Now i want

[Anoop P_2]

Hi

I see the setup is already in an unrecommended fashion.

There are five disks in the VG, but only four are in the PVG group.

LVs from lvsapmnt to lvsapdata4 are created with PVG Strict allocation. When creating the rest, no such allocation policy was probabily used, so it looks like all of them have Used PV=1.

Since the disks in PVG are already used for allocation outside the policy, your best way is to add up another 4 luns. It is advisable to use a second PVG and you can mention the name of this PVG with the lvextend command.

Hope this helps.

[R.K. #]

Hello Jsk,

> I need to increase 4 of the lvols

Which lvols needs to be increased?
Please attach lvdisplay o/p for them to check the lvm policy implemented there.

Regds..

[jsk_cbe]

eoerr3p@root:/> lvdisplay -v /dev/vgsap/lvsapdata1 |more
--- Logical volumes ---
LV Name /dev/vgsap/lvsapdata1
VG Name /dev/vgsap
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 71680
Current LE 8960
Allocated PE 8960
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation PVG-strict/distributed
IO Timeout (Seconds) default

--- Distribution of logical volume ---
PV Name LE on PV PE on PV
/dev/disk/disk54 2240 2240
/dev/disk/disk55 2240 2240
/dev/disk/disk56 2240 2240
/dev/disk/disk57 2240 2240

--- Logical extents ---
LE PV1 PE1 Status 1
00000 /dev/disk/disk54 01620 current
00001 /dev/disk/disk55 01619 current
00002 /dev/disk/disk56 01619 current
00003 /dev/disk/disk57 01619 current
00004 /dev/disk/disk54 01621 current
00005 /dev/disk/disk55 01620 current
00006 /dev/disk/disk56 01620 current
00007 /dev/disk/disk57 01620 current

i want to increase lvsapdata1 to lvsapdata4 all are of same size and same policy.