Hi, I had the same error message doing while fsck'ing one of my disks. I did not understand well the cause of the problem. Is fsck what caused the file-system corruption? (because of an "extent-mapped inode getting written (or copied) to a different/wrong place in the inode table"?)
This ticket is labelled e2fsprogs. May you explain if the planned fix is: - to avoid file-system corruption - to enable fsck to fix it (- something else?) please? -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
