From: "Dâniel Fraga" <fragabr@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Andreas Dilger <adilger@dilger.ca>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: Kernel 3.7.0: bad header/extent
Date: Sun, 16 Dec 2012 21:52:49 -0200 [thread overview]
Message-ID: <50ce5ed5.8991ec0a.0f36.4b12@mx.google.com> (raw)
In-Reply-To: <20121216145013.GA5098@thunk.org>
On Sun, 16 Dec 2012 09:50:13 -0500
Theodore Ts'o <tytso@mit.edu> 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
prev parent reply other threads:[~2012-12-16 23:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-15 20:44 Kernel 3.7.0: bad header/extent Dâniel Fraga
2012-12-16 2:27 ` Theodore Ts'o
2012-12-16 3:00 ` Dâniel Fraga
2012-12-16 3:51 ` Theodore Ts'o
2012-12-16 5:39 ` Dâniel Fraga
2012-12-16 6:08 ` Andreas Dilger
2012-12-16 14:50 ` Theodore Ts'o
2012-12-16 23:52 ` Dâniel Fraga [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50ce5ed5.8991ec0a.0f36.4b12@mx.google.com \
--to=fragabr@gmail.com \
--cc=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).