From: Andreas Dilger <adilger@clusterfs.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19pre8aa3
Date: Wed, 15 May 2002 15:56:21 -0600 [thread overview]
Message-ID: <20020515215621.GE12975@turbolinux.com> (raw)
In-Reply-To: <20020515212733.GA1025@dualathlon.random>
On May 15, 2002 23:27 +0200, Andrea Arcangeli wrote:
> Only in 2.4.19pre8aa3: 00_ext3-register-filesystem-lifo-1
>
> Make sure to always try mounting with ext3 before ext2 (otherwise
> it's impossible to mount the real rootfs with ext3 if ext3 is a module
> loaded by an initrd and ext2 is linked into the kernel).
Hmm, I don't think this is true. While I'm not an initrd user, people
have been doing this with RH for quite some time. Note that it is not
necessarily true that they get it _correct_ all the time, but eventually
it works. Apparently you need to explicitly specify the root filesystem
type for the initrd mount.
Note that I haven't seen the patch in question yet (mirrors don't have
it), but somehow I don't think that changing the order of the
registration is going to help. If they have both ext2 and ext3 as
modules, and insmod ext3 first and ext2 second, you've just broken
their setup. Similarly, (depending on how it is done) I imagine this
would break kernels that have both ext3 and ext2 compiled in.
The only reasonable solution is to not guess at the root filesystem type
and mount it with the correct type explicitly. I think the RH mkinitrd
will check /etc/filesystems for the root fs and use the type there. If
the user forgets to run mkinitrd after changing their kernel, there is
not much you can do about that.
What _may_ be helpful is if ext2 printed a small warning that it is
mounting a filesystem with a journal as ext2 and no journaling will
be done, if the user really wanted to do that (normally they will not).
This will at least alert some users that their root filesystem is not
being mounted as ext3 and eliminate a number of support requests on
ext2-devel when initrd users are wondering why e2fsck is being run on
their supposedly journaled filesystem. The fact that "mount" output
shows ext3 as the filesystem type (while 'cat /proc/mounts' shows ext2)
does nothing to help the user figure out what is wrong.
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
next prev parent reply other threads:[~2002-05-15 21:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 21:27 2.4.19pre8aa3 Andrea Arcangeli
2002-05-15 21:56 ` Andreas Dilger [this message]
2002-05-16 2:18 ` 2.4.19pre8aa3 Andrea Arcangeli
2002-05-15 22:30 ` 2.4.19pre8aa3 Rik van Riel
2002-05-16 2:01 ` 2.4.19pre8aa3 Andrea Arcangeli
2002-05-16 2:06 ` 2.4.19pre8aa3 Rik van Riel
2002-05-16 2:32 ` 2.4.19pre8aa3 Andrea Arcangeli
2002-05-16 2:42 ` 2.4.19pre8aa3 Rik van Riel
2002-05-16 2:58 ` 2.4.19pre8aa3 Andrea Arcangeli
2002-05-16 8:36 ` 2.4.19pre8aa3 Russell King
2002-05-16 8:59 ` 2.4.19pre8aa3 Russell King
2002-05-16 12:56 ` 2.4.19pre8aa3 Andrea Arcangeli
2002-05-16 9:27 ` 2.4.19pre8aa3 Juan Quintela
2002-05-16 16:07 ` 2.4.19pre8aa3 Andrea Arcangeli
2002-05-16 18:37 ` 2.4.19pre8aa3 Rik van Riel
2002-05-16 18:59 ` 2.4.19pre8aa3 Andrea Arcangeli
2002-05-16 3:12 ` 2.4.19pre8aa3 Andrew Morton
2002-05-16 3:23 ` 2.4.19pre8aa3 Andrea Arcangeli
2002-05-16 19:26 ` 2.4.19pre8aa3 Christoph Hellwig
2002-05-31 20:34 ` 2.4.19pre8aa3 Andrea Arcangeli
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=20020515215621.GE12975@turbolinux.com \
--to=adilger@clusterfs.com \
--cc=andrea@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®