Re: can't read superblock on a xfs partition

On Wed, 28 Dec 2005 14:16:23 +0100, Nicolas <aragorn_700@xxxxxxxx> wrote:

- I use xfs over lvm with xfs version 2.6.25 and try xfs 2.7.3too

The mistake :
- I made :
lvextend -L +100G /dev/jbod2/export
xfs_growfs /export
*sic*
( in place of : xfs_growfs /dev/jbod2/export )


Another thought: Is there any chance that xfg_growfs is intelligent
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?

If that is the actual problem, it may be possible to construct a
solution, if the data are sufficiently valuable, by studying the
order of the operations of xfs_growfs, and looking at the data on
the disks.

-Enrique
.

Relevant Pages

  • 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. ... > 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)