lvextending a PVG-Strict, Distributed lv with PVs of different sizes?

[ricardor_1]

Hello There,

We have a PVG-Strict LV set with Distributed allocation. We want to lvextend it, but our PVs are of different sizes.

For instance, we´ll add:

2x36 gb + 1x13gb

Is it possible to lvextend it to all the PEs while keeping the distributed allocation policy?

Thank you.

[Tim Nelson]

No.

Either you will have to completely re-build the distributed stripe or turn off the strict policy and let the vg expansion run sequetially to the last disk

Once a distributed lvol is created there is no adding to it.

[Tim Nelson · Accepted solution]

No.

Either you will have to completely re-build the distributed stripe or turn off the strict policy and let the vg expansion run sequetially to the last disk

Once a distributed lvol is created there is no adding to it in a distruted fashion.

[ricardor_1]

Thank you!

I´ve just noticed the LV I´m reffering to is set to PVG-Strict but no PVG-Strict/distributed. It´s probably been already extended, since the first LEs are shown as below:

PV Name LE on PV PE on PV
/dev/dsk/ch4t0d0 2302 2302
/dev/dsk/ch4t0d3 2302 2302
/dev/dsk/ch4t0d6 2302 2302

And the last ones:

09205 /dev/dsk/ch4t2d4 02299 current
09206 /dev/dsk/ch4t2d4 02300 current
09207 /dev/dsk/ch4t2d4 02301 current

You mean I should disable only the DISTRIBUTED policy, not the pvg-strict (-s g), right? So I suppose the LV is probably already in the shape to be lvextended?


Thank you again.

[Sandman!]

According to your last post it looks like the LV is neither PVG-strict nor is it distributed...otherwise every successive LE would reside on a different PV. Could you post the attributes of the LV in question i.e.

# lvdisplay /dev/vg??/lvol??

[ricardor_1]

--- Logical volumes ---
LV Name /dev/vgbild1/pbil01
VG Name /dev/vgbild1
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 147328
Current LE 9208
Allocated PE 9208
Stripes 0
Stripe Size (Kbytes) 0
Bad block NONE
Allocation PVG-strict
IO Timeout (Seconds) default


Thank you all again.

[Sandman!]

The LVOL in question is not mirrored so the PVG-strict allocation policy in this case is meaningless. You can go ahead and lvextend the LVOL normally. Just for the sake of clarity could you post the contents of the "/etc/lvmpvg" file i.e.

# cat /etc/lvmpvg

[ricardor_1]

VG /dev/vgbild1
PVG pvgvgbild1
/dev/dsk/ch4t0d0
/dev/dsk/ch4t0d3
/dev/dsk/ch4t0d6
/dev/dsk/ch4t2d4


I´ve successfully extended the LVs and the associated filesystem. Thank you all for your prompt support!

[ricardor_1]

Thanks!