From: "Stephen C. Tweedie" <sct@redhat.com>
To: Steve Dodd <steved@loth.demon.co.uk>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
ext3-users@redhat.com, Florian Lohoff <flo@rfc822.org>,
linux-kernel@vger.kernel.org
Subject: Re: ext3 message if FS is not ext3
Date: Mon, 28 May 2001 10:37:50 +0100 [thread overview]
Message-ID: <20010528103750.C12466@redhat.com> (raw)
In-Reply-To: <20010523140013.A883@paradigm.rfc822.org> <20010523130616.B8080@redhat.com> <20010526105439.A7302@lilith.loth.demon.co.uk>
In-Reply-To: <20010526105439.A7302@lilith.loth.demon.co.uk>; from steved@loth.demon.co.uk on Sat, May 26, 2001 at 10:54:39AM +0100
Hi,
On Sat, May 26, 2001 at 10:54:39AM +0100, Steve Dodd wrote:
> On Wed, May 23, 2001 at 01:06:16PM +0100, Stephen C. Tweedie wrote:
> > On Wed, May 23, 2001 at 02:00:13PM +0200, Florian Lohoff wrote:
>
> > > i think this message should be removed ;)
> [..]
> > > VFS: Can't find an ext3 filesystem on dev fd(2,0).
>
> > mount(8) tried to get the kernel to mount /dev/fd0 as an ext3
> > filesystem. The kernel is entitled to emit an error in that case.
> > ext2 will complain too.
>
> Shouldn't it be doing the mount 'silently' when mount(8) is guessing the
> filesystem type? I'm seeing this too (2.2.19 + ext3 0.0.6b):
That's possible. There is actually a "silent" parameter passed to the
filesystem mount routines in the kernel. Unfortunately, it's actually
encoded as a "mount-root" parameter, and it gets used when attempting
the initial root mount when we don't know the filesystem type in
advance. Ext2/ext3 interpret the mount-root parameter as an
instruction to fail silently, but I'm not sure whether there are other
filesystems which actually use it as a hint to treat the root
differently. If so, we can't overload that parameter to mean
go-silent. That's no big deal, we can create a new MS_* flag for
it in that case.
> As the kernel (2.2 or 2.4) doesn't seem to provide a way for userspace to
> request a silent mount, I don't know whose (if anyone's) bug this is.
It's not a bug. It is a missing feature, perhaps.
Cheers,
Stephen
prev parent reply other threads:[~2001-05-28 10:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010523140013.A883@paradigm.rfc822.org>
[not found] ` <20010523130616.B8080@redhat.com>
2001-05-26 9:54 ` ext3 message if FS is not ext3 Steve Dodd
2001-05-28 9:37 ` Stephen C. Tweedie [this message]
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=20010528103750.C12466@redhat.com \
--to=sct@redhat.com \
--cc=ext3-users@redhat.com \
--cc=flo@rfc822.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steved@loth.demon.co.uk \
/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