From: Ted Ts'o <tytso@mit.edu>
To: "Bill Huey (hui)" <bill.huey@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext4 corruption
Date: Mon, 28 Feb 2011 17:55:59 -0500 [thread overview]
Message-ID: <20110228225559.GK28617@thunk.org> (raw)
In-Reply-To: <AANLkTimoODjtQY2mmfgnPMisEA+kUNeEnGryL1CMgAFM@mail.gmail.com>
On Mon, Feb 28, 2011 at 12:18:16PM -0800, Bill Huey (hui) wrote:
> What ever is in the latest Ubuntu maverick, 2.6.35 for the kernel.
>
> The only thing that makes it not looking like it was a storage problem
> is this line that comes before the SATA error:
>
> -----
> Feb 25 04:41:26 finfin kernel: [206290.181230] JBD: Spotted dirty
> metadata buffer (dev = sdb1, blocknr = 0). There's a risk of
> filesystem corruption in case of system crash.
> -----
There are a few places where we update the superblock bypassing the
journal layer. (For example, when we set the RO_COMPAT_LARGE_FILE
feature flag if it wasn't previously set). Those should be cleaned
up, but it's not related to the rest of the scary-looking corruption
which you saw. The worst that might happen is specific superblock
update might get lost (i.e., the RO_COMPAT_LARGE_FILE feature flag) on
a crash before we commit some other superblock change to the journal.
- Ted
next prev parent reply other threads:[~2011-02-28 22:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-26 10:16 ext4 corruption Bill Huey (hui)
2011-02-26 11:10 ` Theodore Tso
2011-02-26 11:13 ` Bill Huey (hui)
2011-02-26 11:16 ` Bill Huey (hui)
2011-02-28 4:43 ` Ted Ts'o
2011-02-28 20:18 ` Bill Huey (hui)
2011-02-28 20:30 ` Bill Huey (hui)
2011-02-28 22:55 ` Ted Ts'o [this message]
2011-02-28 23:45 ` Bill Huey (hui)
2011-02-28 15:01 ` Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2011-06-06 3:59 Micah Anderson
2011-06-06 4:19 ` Ted Ts'o
2011-06-06 17:11 ` micah anderson
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=20110228225559.GK28617@thunk.org \
--to=tytso@mit.edu \
--cc=bill.huey@gmail.com \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).