invalid inode numbers ? after drive moved from Linux 2.6.32 to Linux 3.16.0 then back again

From: Nigel Tamplin <ntamplin@codefaber.co.uk>
To: xfs@oss.sgi.com
Subject: invalid inode numbers ? after drive moved from Linux 2.6.32 to Linux 3.16.0 then back again
Date: Wed, 8 Jun 2016 12:16:10 +0100	[thread overview]
Message-ID: <5757FE7A.8020504@codefaber.co.uk> (raw)

Hello,

I have a drive with a partition containing an XFS file system.
This drive normally resides in a Linux 2.6.32 (Debian 6) server, which 
is also where the file system was created many months ago.
Last week I removed this drive from it's usual 2.6.32 server and for a 
few hours it was attached to an alternative Linux 3.16.0 (Debian 8) 
server, where the XFS file system was mounted and during this time I 
created /modified / deleted some files.
Later the drive was moved back to the normal Linux 2.6.32.

I've noticed something strange has happened.
Some (maybe all) of the files worked on whilst the drive was in the 
Linux 3.16.0 are not accessible when the file system is mounted on the 
Linux 2.6.32.

If I put the drive back in the 3.16.0 server, all files are again 
accessible.

The few files which are inaccessible on 2.6.32 seem to have no inodes 
when viewed under 2.6.32 but look ok when the drive is in 3.16.0

"ls -li" on 3.16.0

7249604387 drwxrwxr-x 2 nigel users      118 Jun  2 16:40 01
     104207 drwxrwxr-x 2 nigel users     4096 Jun  2 16:40 02
     101524 drwxrwxr-x 2 nigel users       62 Jun  2 16:39 03
2220005080 drwxrwxr-x 2 nigel users      118 Jun  2 16:40 06
5637828101 drwxrwxr-x 2 nigel users      118 Jun  2 16:40 07
1344499710 drwxrwxr-x 2 nigel users      118 Jun  2 16:40 09
2958135019 drwxrwxr-x 2 nigel users       62 Jun  2 16:39 0b
7516254020 drwxrwxr-x 2 nigel users     4096 Jun  2 16:40 0c
5905580833 drwxrwxr-x 2 nigel users     4096 Jun  2 16:40 0f
3494120096 drwxrwxr-x 2 nigel users     4096 Jun  2 16:40 10
1988369908 drwxrwxr-x 2 nigel users       62 Jun  2 16:40 12
2446706848 drwxrwxr-x 2 nigel users       62 Jun  2 16:40 13
2446706832 drwxrwxr-x 2 nigel users     4096 Jun  2 16:40 14
5905580836 drwxrwxr-x 2 nigel users       62 Jun  2 16:40 16
  807056393 drwxrwxr-x 2 nigel users     4096 Jun  2 16:40 17
2688006922 drwxrwxr-x 2 nigel users       62 Jun  2 16:40 18

"ls -li" on 2.6.32

          ? ?????????? ? ?     ?            ?            ? 01
     104207 drwxrwxr-x 2 nigel users     4096 Jun  2 16:40 02
     101524 drwxrwxr-x 2 nigel users       62 Jun  2 16:39 03
2220005080 drwxrwxr-x 2 nigel users      118 Jun  2 16:40 06
          ? ?????????? ? ?     ?            ?            ? 07
1344499710 drwxrwxr-x 2 nigel users      118 Jun  2 16:40 09
2958135019 drwxrwxr-x 2 nigel users       62 Jun  2 16:39 0b
          ? ?????????? ? ?     ?            ?            ? 0c
          ? ?????????? ? ?     ?            ?            ? 0f
3494120096 drwxrwxr-x 2 nigel users     4096 Jun  2 16:40 10
1988369908 drwxrwxr-x 2 nigel users       62 Jun  2 16:40 12
2446706848 drwxrwxr-x 2 nigel users       62 Jun  2 16:40 13
2446706832 drwxrwxr-x 2 nigel users     4096 Jun  2 16:40 14
          ? ?????????? ? ?     ?            ?            ? 16
  807056393 drwxrwxr-x 2 nigel users     4096 Jun  2 16:40 17
2688006922 drwxrwxr-x 2 nigel users       62 Jun  2 16:40 18

I notice that the files created on 3.16.0 which cannot be accessed on 
2.6.32, seem to have much higher inode numbers than those which can be 
accessed on both systems.  Could the numbers chosen by 3.16.0 be 
overflowing on 2.6.32 ?  I experimented on another almost empty file 
system, and this seems fine in both systems, but this has very low inode 
numbers, hence my inode number idea.

I can attach the drive to either system and run diagnostic commands if 
more information is required.

Regards,
Nigel

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs