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
The direct and indirect block values just looked odd to me. For example, I wasn't expecting a double or tripple indirect block based on the file size. But I also wasn't aware mi doesn't support extents yet. So if I ignore the direct/indirect blocks things look ok. Please let me know if you manage to craft an fsck which detects the corrupted extent header. We have probably 10 or so ldiskfs devices with damage similar to this so we've got lots of places to verify it works! I may fix one or two as best as I can for now by simply zeroing out the direct/indirect blocks in the inode, and verifiying that's the only issue. _______________________________________________ Lustre-devel mailing list [email protected] https://mail.clusterfs.com/mailman/listinfo/lustre-devel
