From: Andrew Morton <akpm@digeo.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: viro@math.psu.edu, linux-kernel@vger.kernel.org
Subject: Re: [2.5.51] Failure to mount ext3 root when ext2 compiled in
Date: Thu, 12 Dec 2002 20:09:52 -0800 [thread overview]
Message-ID: <3DF95D90.DEE68C66@digeo.com> (raw)
In-Reply-To: 20021213035016.339092C24F@lists.samba.org
Rusty Russell wrote:
>
> Just noticed this (usually ext2 is compiled as a module, but was
> testing a patch with CONFIG_MODULES=n). Reverted to plain 2.5.51, and
> it's still there:
>
> VFS: Cannot open root device "301" or 03:01
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on 03:01
>
> Now, I have an ext3 root, but when CONFIG_EXT3_FS=y and
> CONFIG_EXT2_FS=y, I get this failure. Turning off CONFIG_EXT2_FS
> "fixes" it.
>
In the past year I've booted about 1,000,000,000 kernels with
CONFIG_EXT2_FS=y and CONFIG_EXT3_FS=y. Across that period,
maybe five or ten times I have seen this problem.
As soon as I get down to debug it it goes away. I once traced it
as far as seeing ext3_fill_super() return failure, then I lost it.
Rebuilding the kernel, even if you "didn't change anything" makes
it go away.
I assume that in your case a `make clean' will not fix it. You
lucky duck. Can you stick a printk right at the end of
ext3_fill_super()?
next prev parent reply other threads:[~2002-12-13 4:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 3:48 [2.5.51] Failure to mount ext3 root when ext2 compiled in Rusty Russell
2002-12-13 4:09 ` Andrew Morton [this message]
2002-12-16 21:42 ` Rusty Russell
2002-12-13 14:31 ` Wayne Willson
-- strict thread matches above, loose matches on Subject: below --
2002-12-13 14:35 Mohamed El Ayouty
2002-12-14 10:11 ` Andrew Morton
2002-12-14 14:22 ` Mohamed El Ayouty
2002-12-14 18:48 ` Andrew Morton
2002-12-14 19:06 ` Mohamed El Ayouty
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=3DF95D90.DEE68C66@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=viro@math.psu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.