do SG logical volumes need to be strict allocation?

[Rick Garland]

Hi all:

MCSG 11.16 on 11i
Doing some LV extension.

Have halted cluster, made the VGs unsharable, changes to exclusive mode, and now I am doing the lvextend.

I have 2 out of 3 LVs extended. The 3rd lvextend fails because of strict allocation. Do the LVs with a shared VG need to be strict allocation?

[IT_2007]

No. Unless you need it.

You won't be able to extend it because it was already created with "strict allocation" policy.

[Rick Garland]

Can I not lvchange -s n /dev/VGname/LVname to turn off the strict policy?

Will this allow me to extend a MCSG logical volume without troubles?

Does the MCSG have to remain strict? Even though it was created this way.

[Marvin Strong]

You can just disable it lvchange and you can then extend it, but there might be a reason it was set to strict.

[IT_2007]

yes. You can do it on the fly. But if you sure that there is no reason to be like that then you can change it.

I tested it now:

lvchange -s n /dev/vg01/lvol9
Logical volume "/dev/vg01/lvol9" has been successfully changed.
Volume Group configuration for /dev/vg01 has been saved in /etc/lvmconf/vg01.conf

[James R. Ferguson · Accepted solution]

Hi Rick:

Serviceguard aside, strict allocation is set by default when a logical volume is created. The idea, of course, is to prevent mirrored extents from sharing the same physical volume or physical volume group when PVG-strict allocation is set.

Regards!

...JRF...