Thanks, I was able to reproduce the problem using a test file system.
The problem appears to have been caused by an extent-mapped inode
getting written (or copied) to a different/wrong place in the inode
table. I should be able to get this fixed now that I have a simple
repro.
** Changed in: e2fsprogs (Ubuntu)
Status: New => Confirmed
** Changed in: e2fsprogs (Ubuntu)
Assignee: (unassigned) => Theodore Ts'o (tytso)
--
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
