From: "Ted Ts'o" <tytso@mit.edu>
To: Frej Eriksson <frej.eriksson@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fwd: ext4 extents.c bug
Date: Tue, 13 Mar 2012 18:00:01 -0400 [thread overview]
Message-ID: <20120313220000.GC11969@thunk.org> (raw)
In-Reply-To: <CACbLGLLLtD8TJd-VvdkQYo48nT5NFE8bmH8aHtwy6-hoCbqL9g@mail.gmail.com>
On Tue, Mar 13, 2012 at 09:14:18PM +0100, Frej Eriksson wrote:
>
> Thank you for your the information! If i get you correct does it mean
> that you need to have an updated version of both the kernel and
> e2fsprogs in order to have the issue fixed? Or is it enough to run
> e2fsprogs with the patch applied?
If you run e2fsprogs with the patch applied, it will fix the file
system corruption that caused your kernel to BUG. If the file system
corruption happens again (for whatever reason; kernel bug, hardware
problem, etc.) then the kernel will BUG instead of printing an
"EXT4-fs error" message and marking the file system as corrupted.
If you have your file system set to "tune2fs -e panic" there will be
no difference (since after the error message the kernel will be forced
to reboot so e2fsck can fix the problem). But if you have your file
system set to "tune2fs -e continue" or "tune2fs -c read-only", where
you prefer that the file system be mounted read-only or just simply
continue after noting a file system corruption problem, and you want
that behavior, then you'd have to apply the kernel patch as well.
(You can see what the corrent behaviour on file systems errors by
looking at the output of "dumpe2fs -h /dev/sdXX | grep ^Errors".)
Regards,
- Ted
prev parent reply other threads:[~2012-03-13 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACbLGLK8ZLLHzykKb8LRZO+x+_Cqe6r_dna1=QC4nDGSyWrfNw@mail.gmail.com>
2012-03-13 19:39 ` Fwd: ext4 extents.c bug Frej Eriksson
2012-03-13 19:57 ` Ted Ts'o
2012-03-13 20:14 ` Frej Eriksson
2012-03-13 22:00 ` Ted Ts'o [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=20120313220000.GC11969@thunk.org \
--to=tytso@mit.edu \
--cc=frej.eriksson@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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