Re: changing contiguous strict allocation policy

From: Lars Bausch (lars.bausch_at_dotsch.de)
Date: 10/23/05


Date: Sun, 23 Oct 2005 12:18:55 +0200

Hi !

yls177 wrote:
> i was trying to lvextend one of my file system (this belongs to one of
> my applications) but got the below messages
>
> lvextend: Not enough free physical extents available.
> Failure possibly caused by contiguous allocation policy.
> Failure possibly caused by strict allocation policy
>
> I have checked that this logical volume is 2 disks, one is for mirror,
> and a pvdisk shows enough disk space
>
>
> i did a lvchance -Cn /dev/vgxx/.... before i lvextend.
>
> Did i do the right thing?
You have to do a "lvchange -s n /dev/vgXX/lvolYY", too.

Lars



Relevant Pages

  • changing contiguous strict allocation policy
    ... lvextend: Not enough free physical extents available. ... Failure possibly caused by contiguous allocation policy. ... and a pvdisk shows enough disk space ...
    (comp.sys.hp.hpux)
  • Re: changing contiguous strict allocation policy
    ... > lvextend: Not enough free physical extents available. ... > I have checked that this logical volume is 2 disks, one is for mirror, ... > and a pvdisk shows enough disk space ... You must have enough free extents in both used disks if lv is in "strict mode" and do not forget you ...
    (comp.sys.hp.hpux)