Right, I didn't notice the first time I read the bug report you had already deleted the inode to fix the problem. It would have been nice to have gotten a look at the inode in question so I could really see what was going on.
The "internal error: can't find dup_blk" error is one of those "this should never happen" situations, so it would be good to understand how and why it happened, and hopefully figure out how to reproduce it. Can you send me the output of dumpe2fs -h /dev/md/1, just for the record? Thanks!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321418 Title: fsck.ext4 fails to fix multiply-claimed blocks: can't find dup_blk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1321418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
