From: Andreas Dilger <adilger@clusterfs.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: Andrew Morton <akpm@digeo.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.20-rc1 dirty ext2 mount error
Date: Wed, 6 Nov 2002 01:41:43 -0700 [thread overview]
Message-ID: <20021106084143.GN588@clusterfs.com> (raw)
In-Reply-To: <21861.1036564011@kao2.melbourne.sgi.com>
On Nov 06, 2002 17:26 +1100, Keith Owens wrote:
> Unclean shutdown, reboot.
>
> LILO boot: 2.4.20-rc1
> Loading 2.4.20-rc1........................
> Linux version 2.4.20-rc1 (kaos@sherman) (gcc version 3.2 20020822 (Red Hat Linux Rawhide 3.2-4)) #10 SMP Wed Nov 6 16:10:31 EST 2002
> Kernel command line: auto BOOT_IMAGE=2.4.20-rc1 ro root=801 BOOT_FILE=/lib/modules/2.4.20-rc1/bzImage console=tty0 console=ttyS0,38400 mem=127M
> EXT2-fs: sd(8,1): couldn't mount because of unsupported optional features (4).
> Kernel panic: VFS: Unable to mount root fs on 08:01
>
> Entering kdb (current=0xc11f4000, pid 1) on processor 1 due to KDB_ENTER()
> [1]kdb> reboot
>
> Come up on 2.4.18-14 from RH. It detects ext3 and cleans the journal,
> even though fstab says ext2. Then ext2 does fsck.ext2 -a /dev/sda1. I
> guess the question is why ext3 is being used when fstab says ext2?
> Especially when that stuffs up booting into other kernels that do not
> have ext3 support at all.
/etc/fstab is not available until after the kernel mounts the root
filesystem, so what is in /etc/fstab is totally irrelevant here.
If you don't simultaneously crash your system running ext3, and then reboot
into a kernel which does not support ext3 you will be fine. A clean
shutdown will clear the "needs_recovery" flag (and any ext2-only kernel
can blissfully use that filesystem), any ext3-aware kernel can also
mount it again and do a journal flush, or any modern (last year or two)
e2fsck will clean it up too (from a rescue disk if desparate).
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
next prev parent reply other threads:[~2002-11-06 8:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 5:35 2.4.20-rc1 dirty ext2 mount error Keith Owens
2002-11-06 5:46 ` Andrew Morton
2002-11-06 6:26 ` Keith Owens
2002-11-06 8:28 ` Matt Bernstein
2002-11-06 8:41 ` Andreas Dilger [this message]
2002-11-06 10:43 ` Keith Owens
2002-11-06 11:21 ` Willy Tarreau
2002-11-06 16:39 ` Theodore Ts'o
2002-11-06 10:00 ` James H. Cloos Jr.
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=20021106084143.GN588@clusterfs.com \
--to=adilger@clusterfs.com \
--cc=akpm@digeo.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@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 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.