From: Karel Zak <kzak@redhat.com>
To: Benno Schulenberg <bensberg@justemail.net>
Cc: Util-Linux <util-linux@vger.kernel.org>
Subject: Re: when specifying multiple types, mount will mount
Date: Fri, 25 Jul 2014 10:32:16 +0200 [thread overview]
Message-ID: <20140725083216.GO26781@x2.net.home> (raw)
In-Reply-To: <1406233871.13212.145356397.0035B2A9@webmail.messagingengine.com>
On Thu, Jul 24, 2014 at 10:31:11PM +0200, Benno Schulenberg wrote:
> Current mount (2.25) will always mount a device when more
> than one type is given in a comma-separated list. Older mount
> (2.17.2 for example) would not not do that but error out.
We want to support list-of-types in fstab and on command line.
> For example, /dev/sda2 is of type ext4, but we are playing dumb,
> to see what mount will say:
>
> $ sudo ./mount /dev/sda2 /place -t btrfs
> lt-mount: /dev/sda2: can't read superblock
>
> $ sudo ./mount /dev/sda2 /place -t msdos
> lt-mount: wrong fs type, bad option, bad superblock on /dev/sda2,
> missing codepage or helper program, or other error
>
> In some cases useful info is found in syslog - try
> dmesg | tail or so.
>
> $ sudo ./mount /dev/sda2 /place -t btrfs,msdos
this is bug, it continues with /{proc,etc}/filesystems when no found
anything useful in the list.
> $ ./mount | grep sda2
> /dev/sda2 on /place type ext4 (rw)
>
> I find this surprising. If -t does not support a comma-separated
> list, it should report an error. If it does, it should, IMO, only
> try the specified types and not any others.
yes, I'm just working on patch and regression test for all -t
use-cases.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2014-07-25 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 20:31 when specifying multiple types, mount will mount Benno Schulenberg
2014-07-25 8:32 ` Karel Zak [this message]
2014-07-25 11:11 ` Karel Zak
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=20140725083216.GO26781@x2.net.home \
--to=kzak@redhat.com \
--cc=bensberg@justemail.net \
--cc=util-linux@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;
as well as URLs for NNTP newsgroup(s).