I don't know if this is the answer to your specific problem, but it might be relevant:
"ext3 filesystems may still be mounted by ext2 as long as they have been cleanly unmounted. ext2 will refuse to mount ext3 filesystems which have not been cleanly shut down, because there is live data still in the journal which ext2 does not know how to deal with. "The e2fsck application from e2fsprogs can perform journal replay, so running e2fsck -fy /dev/hdXX on a damaged ext3 filesystem will repair it, allowing ext2 to mount it. "ext3 software will refuse to mount an ext2 filesystem - at present there must be a journal file on the filesystem." I found that here: http://www.uow.edu.au/~andrewm/linux/ext3/ext3-usage.html Of course, it wouldn't hurt to patch your kernel for ext3 support (I've been using the -ac kernels with no problems, but I hear that a merge is imminent). You might also make sure that e2fsprogs and util-linux are up to date. -jacob On Fri, 2001-11-02 at 13:16, Spencer Ogden wrote: > I am trying to escape from the swap storm hell that is 2.4.8 ( I assume that > is what is happening when the HD is churning, then X gets less responsive, > then finally no response, and no slowdown in HD churning after 10-15 minutes, > finally hard rebooting). > > So I have compiled 2.4.13. Everything seems fine, except when I boot I get a > Kernel Panic saying that it can't mount the root ext2 partition due to extra > options. The root is ext3, but I was under the impression that ext3 could be > booted as ext2 with just a loss of Journalling features. Where should I start > to look for answers? Should I patch the kernel for ext3 support? > > Spencer _______________________________________________ Siglinux mailing list [EMAIL PROTECTED] http://www.utacm.org/mailman/listinfo/siglinux
