LVM and VxVM

lvextend issue--caused by strict allocation policy

 
fizan
Super Advisor

lvextend issue--caused by strict allocation policy

Hi All,

lvextend -L 512 /dev/vg01/ora_testlv
lvextend: Not enough free physical extents available.
Logical volume "/dev/vg01/ora_testlv" could not be extended.
Failure possibly caused by strict allocation policy
=============================================



































































7 REPLIES 7
Ivan Krastev
Honored Contributor

Re: lvextend issue--caused by strict allocation policy

Check the number of available free extents in the VG per disk:

vgdisplay -v /dev/vg01


regards,
Ivan
fizan
Super Advisor

Re: lvextend issue--caused by strict allocation policy

PE Size (Mbytes) 4
Free PE 900

# 3GB free space is there, my question is anyting to do with allocation policy?
Ivan Krastev
Honored Contributor

Re: lvextend issue--caused by strict allocation policy

At the bottom you will see how many free PE you have per disk.
Plese provide the full output of the command.
fizan
Super Advisor

Re: lvextend issue--caused by strict allocation policy

Hi Ivan,

its only 90MB free sorry, calculated wrongly, but now the lvextend done, but can i know whats the possible error if i get
"Failure possibly caused by strict allocation policy"
Ivan Krastev
Honored Contributor

Re: lvextend issue--caused by strict allocation policy

If you have logical volume mirrored over 2 disks this allocation policy control how the data are distributed over disks (or pvg groups).

See more info here - http://docs.hp.com/en/B2355-90681/lvchange.1M.html

For example if you have 10MB available on the 1st disk and 110MB on the second total you have 120MB available in the volume group.

But this stric allocation policy will allows you to extend the logical volume only with 10MB - the size of the free space on the 1st disk.

regards,
ivan
Stephenred
Occasional Visitor

Re: lvextend issue--caused by strict allocation policy

how about when u have no extents available on the 1st disk but 494 on the 2nd and it's setup with strict policy..

can u change to policy to non-strict and basically break the mirror?

it's /tmp, i really don't care if it's mirrored..

Thanks

 

Torsten.
Acclaimed Contributor

Re: lvextend issue--caused by strict allocation policy

>> no extents available on the 1st disk but 494 on the 2nd

 

first find out why it is unbalanced.


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!