From: Karel Zak <kzak@redhat.com>
To: Benno Schulenberg <bensberg@justemail.net>
Cc: Util-Linux <util-linux@vger.kernel.org>
Subject: Re: umount: --types does not limit
Date: Tue, 15 Jul 2014 11:56:03 +0200 [thread overview]
Message-ID: <20140715095603.GR30288@x2.net.home> (raw)
In-Reply-To: <1405414924.13201.141769101.02687AE4@webmail.messagingengine.com>
On Tue, Jul 15, 2014 at 11:02:04AM +0200, Benno Schulenberg wrote:
>
> On Tue, Jul 15, 2014, at 10:02, Karel Zak wrote:
> > umount -t <type>
> >
> > the <type> is filesystem type (so you can force umount to use for
> > example /sbin/umount.<type>).
>
> Hmm. But it's not working for me, the --types option does not limit
> umount in any way. In the man page it says: "Indicate that the
> actions should *only* be taken on filesystems of the specified type."
>
> But, for example, here Suse is of type ext4 and gets mounted:
>
> # ./mount -t ext4 /suse
> # ./mount | grep suse
> /dev/sda2 on /suse type ext4 (rw,noatime,noexec,nosuid,nodev,user)
>
> Now I want to unmount all btrfs systems:
>
> # ./umount -t btrfs /suse /zero /other
> # ./mount | grep suse
>
> It just unmounts everything that is mentioned, the -t has no
> limiting effect. So it is useful only with -a.
grrr... you're right, I see.. libmount always overwrites the setting
by stuff from mtab.
IMHO it would be nice to restrict the all the umount actions (like
--recursive, --all-targets or when more mountpoints specified) by the
pattern. I'll add this to the TODO file for v2.26.
Thanks!
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2014-07-15 9:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 9:57 mount: what is the point of 'nouser' on the command line? Benno Schulenberg
2014-07-14 14:57 ` Karel Zak
2014-07-14 15:24 ` Benno Schulenberg
2014-07-15 8:02 ` Karel Zak
2014-07-15 9:02 ` umount: --types does not limit Benno Schulenberg
2014-07-15 9:56 ` Karel Zak [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=20140715095603.GR30288@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