From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@mit.edu>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Eric Sandeen <sandeen@redhat.com>,
linux-ext4@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ext4: oops on boot with root fs needing recovery
Date: Thu, 16 Oct 2008 15:42:55 -0500 [thread overview]
Message-ID: <48F7A74F.5050807@redhat.com> (raw)
In-Reply-To: <20081016203257.GI12962@mit.edu>
Theodore Tso wrote:
> On Thu, Oct 16, 2008 at 01:12:03PM -0700, Jeremy Fitzhardinge wrote:
>> I had a crash and rebooted. The root filesystem needed journal
>> recovery, but ext4 crashed.
>>
>> My root fs is ext3 (no extents), but I've been mounting it as ext4 to
>> see how it turns out.
>
> Yeah, known bug. I'll push a patch to Linus to fix this.
>
> - Ted
>
Jeremy, I see you're using an f10 kernel; it'll be in the next kernel
build there, as well.
-Eric
prev parent reply other threads:[~2008-10-16 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 20:12 ext4: oops on boot with root fs needing recovery Jeremy Fitzhardinge
2008-10-16 20:32 ` Theodore Tso
2008-10-16 20:42 ` Eric Sandeen [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=48F7A74F.5050807@redhat.com \
--to=sandeen@redhat.com \
--cc=jeremy@goop.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@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).