I just got this in dmesg: [67100.343686] Lustre: Found inode with zero generation or link -- this may indicate disk corruption (inode: 26398122/151277060, link 0, count 1) [67100.358660] Lustre: Found inode with zero generation or link -- this may indicate disk corruption (inode: 26398122/151277060, link 0, count 1) [67100.368242] Lustre: Found inode with zero generation or link -- this may indicate disk corruption (inode: 26398122/151277060, link 0, count 1) [67100.368248] Lustre: Skipped 6 previous similar messages [67100.386517] Lustre: Found inode with zero generation or link -- this may indicate disk corruption (inode: 26398114/151277054, link 0, count 1)
So I did run an e2fsck again and among the orphaned inodes e2fsck found in the journal were also these above. This might or might not be a bug in our additional patches for 2.6.20, but its hard to test, since I have not access to your cvs tree for lustre-1.6.1 with 2.6.18 support and older kernels won't run on our hardware. Let me know if there's anything I can do to debug this. Cheers, Bernd -- Bernd Schubert Q-Leap Networks GmbH _______________________________________________ Lustre-discuss mailing list [email protected] https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
