Re: changing contiguous strict allocation policy

From: toto (toto_at_toto.com)
Date: 10/22/05

  • Next message: Lars Bausch: "Re: changing contiguous strict allocation policy"
    Date: Sat, 22 Oct 2005 12:53:27 +0200
    
    

    yls177 wrote:
    > Hi
    >
    > 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?
    >
    > Rgds
    >
    Can we have "vgdisplay -v /dev/vgxx" and "lvdisplay -v /dev/vgxx/lvxx" output ?
    You must have enough free extents in both used disks if lv is in "strict mode" and do not forget you
    need twice the space for mirroring.


  • Next message: Lars Bausch: "Re: changing contiguous strict allocation policy"

    Relevant Pages

    • Re: RAID mirroring, adding disks to vg
      ... Or is that disk space REALLY ... > datavg by 13GB, is it going to allow me? ... use "-c2" on the mklv command to 'mirror' the LV ... > and the other 3 disks for additional copies of the data. ...
      (comp.unix.aix)
    • Re: lvextend: Not enough free physical extents available
      ... > lvextend: Not enough free physical extents available. ... > strict allocation policy means "Mirrors of a logical extent cannot ... With 2 disks in the VG, if all LVs are mirrored, this would be an even number ...
      (comp.unix.admin)
    • Re: 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)
    • 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: cant read superblock on a xfs partition
      ... lvextend -L +100G /dev/jbod2/export xfs_growfs /export *sic* ... enough to determine what device contains the specified directory, i.e., that xfs_growfs was in the middle of doing just the right thing, but you interrupted it when you realized your mistake? ... solution, if the data are sufficiently valuable, by studying the ... the disks. ...
      (comp.os.linux.misc)