From: "Theodore Ts'o" <tytso@mit.edu>
To: Karel Zak <kzak@redhat.com>
Cc: Harald Dunkel <harald.dunkel@aixigo.com>, util-linux@vger.kernel.org
Subject: Re: careful with that umount options, Eugene
Date: Thu, 6 Jun 2019 19:31:47 -0400 [thread overview]
Message-ID: <20190606233147.GB23169@mit.edu> (raw)
In-Reply-To: <20190606125947.6rrdlkhioxx7adwl@ws.net.home>
On Thu, Jun 06, 2019 at 02:59:47PM +0200, Karel Zak wrote:
> On Tue, Jun 04, 2019 at 01:51:58PM +0200, Harald Dunkel wrote:
> > Hi folks
> >
> > by accident I pasted
> >
> > umount ls -al /mnt/
> >
> > into bash. My bad. AFAICT /proc was umounted immediately, the
> > rest died slowly. Don't try this at home.
>
> Fixed ... new version:
>
> # umount ls -al /mnt/
> umount: unexpected arguments
> Try 'umount --help' for more information.
Hmm... Should we also prevent a lazy unmount of the root file system?
- Ted
next prev parent reply other threads:[~2019-06-06 23:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 11:51 careful with that umount options, Eugene Harald Dunkel
2019-06-04 13:55 ` Václav Doležal
2019-06-06 12:59 ` Karel Zak
2019-06-06 23:31 ` Theodore Ts'o [this message]
2019-06-07 7:20 ` Karel Zak
2019-06-07 13:26 ` Theodore Ts'o
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=20190606233147.GB23169@mit.edu \
--to=tytso@mit.edu \
--cc=harald.dunkel@aixigo.com \
--cc=kzak@redhat.com \
--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).