From: Andrew Morton <akpm@zip.com.au>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Rik van Riel <riel@conectiva.com.br>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.19pre8aa3
Date: Wed, 15 May 2002 20:12:04 -0700 [thread overview]
Message-ID: <3CE32384.65C70AA@zip.com.au> (raw)
In-Reply-To: <20020515212733.GA1025@dualathlon.random> <Pine.LNX.4.44L.0205151929430.32261-100000@imladris.surriel.com> <20020516020134.GC1025@dualathlon.random>
Andrea Arcangeli wrote:
>
> ...
> That's all, and that's an autodetection bug because ext3 must be always
> tried first, there's no point at all to try to mount with ext2 before
> ext3 (of course unless rootfstype= is specified).
It is *very* common problem for people to think that their root fs is ext3
when in fact it is being mounted as ext2.
It seems that /etc/mtab incorrectly reports ext3, which doesn't help.
The real truth is revealed in /proc/mounts. (Which has this irritating
"/dev/root" thing in it, btw).
So anything we can do to simplify this problem for people would be
really good. (It would be good if kernel.org came back, too, so we
can see the patch ;))
And Andreas' idea of "Warning: mounting ext3 as as ext2" will help,
too.
--- 2.4.19-pre8/fs/ext2/super.c~ext2-ext3-warning Wed May 15 19:36:12 2002
+++ 2.4.19-pre8-akpm/fs/ext2/super.c Wed May 15 20:11:41 2002
@@ -486,6 +486,9 @@ struct super_block * ext2_read_super (st
bdevname(dev), i);
goto failed_mount;
}
+ if (EXT2_HAS_COMPAT_FEATURE(sb, EXT3_FEATURE_COMPAT_HAS_JOURNAL))
+ ext2_warning(sb, __FUNCTION__,
+ "mounting ext3 filesystem as ext2\n");
sb->s_blocksize_bits =
le32_to_cpu(EXT2_SB(sb)->s_es->s_log_block_size) + 10;
sb->s_blocksize = 1 << sb->s_blocksize_bits;
-
next prev parent reply other threads:[~2002-05-16 3:08 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 ` 2.4.19pre8aa3 Andreas Dilger
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 ` Andrew Morton [this message]
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=3CE32384.65C70AA@zip.com.au \
--to=akpm@zip.com.au \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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®