On Sun, 16 Dec 2012 09:50:13 -0500
Theodore Ts'o <tytso@xxxxxxx> wrote:
> A fix for this was added to e2fsprogs in v1.42.2 in March 2012, by
> commit 26c09eb8145a1 ("e2fsck: check for zero length extent"). There
> was a regression which this commit would sometimes trigger which was
> fixed in v1.42.4 (commit 9c40d14841f0, "e2fsck: only check for
> zero-length leaf extents"). So e2fsck 1.42.4 or newer is recommended
> to repair this sort of file system corruption.
Ok Ted. An easier way was to use Systemrescuecd beta which
provides e2fsck 1.42.6. Now the problem has gone ;)
> I'm not entirely sure how the inode had gotten corrupted in the first
> place, but I would be surprised if it was due to upgrading the kernel
> from 3.6 to 3.7. If you do see this corruption again, please let us
> know, and hopefully we can try to figure out what the root cause of
> the issue might be.
No problem. I always compile my software, so the first time I
notice it was after upgrading to 3.7.0 kernel. Anyway I'm not sure if
it appeared after the upgrade to 3.7.0 kernel.
But ok. If I have some more of these issues, I will report here.
Thanks for the great support!
--
Linux 3.7.0: Terrified Chipmunk
http://www.youtube.com/DanielFragaBR
http://www.libertarios.org.br
--
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
