[2.5.51] Failure to mount ext3 root when ext2 compiled in

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.

Hope this helps,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

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()?

In message <[email protected]> you write:

You have cursed me. Now it works. Looks like a build problem?

Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

I have seen the exact same problem. Turning off CONFIG_EXT2_FS fixes it for me as well.

----- Original Message -----
From: "Rusty Russell" <[email protected]>
To: <[email protected]>; <[email protected]>
Cc: <[email protected]>
Sent: Thursday, December 12, 2002 9:48 PM
Subject: [2.5.51] Failure to mount ext3 root when ext2 compiled in