On Sun, Mar 04, 2012 at 11:11:00PM +0100, Matthias Erll wrote:
>
> In the three cases I can reproduce, the inode number has been identical.
> Please find the debugfs output below.
Thanks, this is helpful. It is indeed a bug in e2fsck; it's not
noticing the case where the extent length is zero (but the extent
header was still valid). The workaround is to run the following
commands with the file system unmounted:
# debugfs -w -R "clri <1312385>" /dev/sda2
# e2fsck -f /dev/sda2
I'll get this fixed in the next maintenance release of e2fsprogs.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
