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
Created an attachment (id=9286) Please don't reply to lustre-devel. Instead, comment in Bugzilla by using the following link: --> (https://bugzilla.lustre.org/attachment.cgi?id=9286&action=view) show block's details in case of ASSERT Brian, could you add this patch to ldiskfs series, rebuild it and rerun so that we know exactly inode and block number. then we'd check on-disk bitmaps with debugfs. next step would be to get the image (e2image <dev> <image-file>; bzip2 -3 <image-file>) and try recent e2fsck to understand why it didn't catch the issue. _______________________________________________ Lustre-devel mailing list [email protected] https://mail.clusterfs.com/mailman/listinfo/lustre-devel
