Logical volume doesn't extend all the luns in the pvg

[rescuehp17]

No problem. I will keep the same set of luns, just in case.

But the question remains, why few LVs doesn't extend to all 11 disks? Is it okay to have the data in couple luns of the PVG before I unmirror and remove the old set of the luns(PVG)?

Thank you!

[Torsten.]

You need to switch back to LE based distribution policy, so the LE will be allocated to each disk one by one.

[rescuehp17]

How is that? I mean, how can I do that? As said, When I mirrored, the Allocation policy of the LVs were PVG-strict/distributed. I was about to unmirror that is the reason I turned those allocation policies off.

[TTr]

We still don't know how the LVOLs are laid out on the old LUNs. This would be in the output of eleven "lvdisplay -v /dev/vgxx/lvolYY" commands. You can run them and create a table summary rather than posting them all.

Your mirroring right now is using 5.5 out of the 11 new LUNs. 

I would mirror each LVOL in a separate new LUN like I posted above and forget about striping. If the array has some kind of backend stripping and virtualization as Torsten mentioned, you should not have any i/o issues.

[Torsten.]

PVG-strict/distributed

is what you want.

PVG strict means LVOLs are mirrored from one PVG to the other.

distributed means

PE1 to disk1

PE2 to disk2

PE3 to disk3

...

[rescuehp17]

Yes, it was PVG-strict/distributed, when I mirrored