On Fri, Apr 08, 2016 at 03:49:17PM -0500, Eric Sandeen wrote:
> Obsolete features do occasionally get dropped upstream, as well - witness
> your V1 inode message. However, that was likely just some other form of
> corruption, seen as V1 inodes, unless this really was a very, very old
> filesystem (created prior to 2007), which seems unlikely.
That error does not come from inode number checking - it is emitted
if the NLINK feature bit is missing from the superblock feature
field.
> On 4/8/16 3:37 PM, Chris M Moser wrote:
> I unmounted and ran xfs_repair 2.9.4 form the host OS a few more
> times.
Is this filesystem was created with 2.9.4, we're talking about a
filesystem that was released:
xfsprogs-2.9.4 (7 Sep 2007)
And, importantly:
xfsprogs-2.9.5 (21 Jan 2008)
- Updated mkfs.xfs defaults.
It was then very next release that sets NLINK by default via:
commit 8d537733f52a642d471f6781f32f306241dd4308
Author: Niv Sardi <xaiki@xxxxxxx>
Date: Fri Nov 16 05:16:34 2007 +0000
....
-
V2 inodes per default, and move DFL bits to XFS_DFL_SB_VERSION_BITS,
Activate XFS_SB_VERSION_NLINKBIT per default, which will enable V2 INODES.
refactor bits that we want everytime in XFS_DFL_SB_VERSION_BITS.
-
....
So, your host has the very last version of xfsprogs that defaulted
to v1 inodes, and so recent xfsprogs versions will simply refuse to
run on it. It does not imply there is any corruption, however, you
just need to use a version of xfs_repair that supports v1 inodes...
Cheers,
Dave.
--
Dave Chinner
david@xxxxxxxxxxxxx
_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs
