Please don't reply to lustre-devel. Instead, comment in Bugzilla by using the
following link:
https://bugzilla.lustre.org/show_bug.cgi?id=11324
Looking at the the inode in some detail also shows some suspicious values.
debugfs: mi <115544101>
Mode [0100600]
User ID [53738]
Group ID [53738]
Size [2428900]
Creation time [1166320440]
Modification time [1166320440]
Access time [1166320440]
Deletion time [0]
Link count [1]
Block count high [0]
Block count [8]
File flags [0x80000]
Generation [0x42c8cdca]
File acl [0]
High 32bits of size [0]
Fragment address [0]
Direct Block #0 [127754]
Direct Block #1 [65540]
Direct Block #2 [19]
Direct Block #3 [6400]
Direct Block #4 [924357007]
Direct Block #5 [0]
Direct Block #6 [3]
Direct Block #7 [95]
Direct Block #8 [924356611]
Direct Block #9 [99]
Direct Block #10 [174]
Direct Block #11 [924356707]
Indirect Block [274]
Double Indirect Block [124]
Triple Indirect Block [924356882]
Alex I've also now run Andreas's latest version with his version of the
extents header checking. It also didn't find any damage, but it's probably
the best place for you to start. I downloaded from the FTP site here:
ftp://ftp.clusterfs.com/pub/lustre/other/e2fsprogs/testing/*-1.39.cfs3*
_______________________________________________
Lustre-devel mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-devel
