public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@ubuntu.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Thomas Orgis <thomas-forum@orgis.org>, util-linux@vger.kernel.org
Subject: Re: losetup -d --force for zombie loop devices?
Date: Tue, 01 May 2012 11:23:42 -0400	[thread overview]
Message-ID: <4F9FFFFE.5070404@ubuntu.com> (raw)
In-Reply-To: <201204301607.22712.vapier@gentoo.org>

On 4/30/2012 4:07 PM, Mike Frysinger wrote:
> `umount -l` has its place -- there are cases where you want those semantics.
> granted, most people actually want a `umount -f`, but the two aren't mutually
> exclusive.
> -mike

If you want to prevent processes from opening new files on the mount 
point, it would be much more sane to mount --move it somewhere hidden. 
When you detach it entirely from the namespace, you can't even be aware 
that the mount still exists, let alone change your mind and reattach it. 
  Having a device that is still mounted, but appears not to be to all 
tools that normally check for such things ( partitioning tools, auto 
mounters, etc ) is broken.

It is very confusing when you later try to change the cd in the drive 
and can't mount it because the old one is still mounted, yet lsof, 
mount, etc offer no evidence that this is the case, and you can't track 
down the process that is still holding an open fd and kill it.


  reply	other threads:[~2012-05-01 15:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17  8:03 losetup -d --force for zombie loop devices? Thomas Orgis
2012-04-17 14:58 ` Mike Frysinger
2012-04-17 21:02   ` Thomas Orgis
2012-04-30 20:03 ` Phillip Susi
2012-04-30 20:07   ` Mike Frysinger
2012-05-01 15:23     ` Phillip Susi [this message]
2012-05-03  4:43       ` Mike Frysinger
2012-05-03 14:29         ` Phillip Susi
2013-01-11 23:52           ` Mike Frysinger
2013-01-12  0:54             ` Phillip Susi
2013-01-12  4:52               ` Mike Frysinger
2013-01-12  5:13                 ` Phillip Susi
2013-01-12  5:29                   ` Mike Frysinger
2013-01-14  8:35                     ` 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=4F9FFFFE.5070404@ubuntu.com \
    --to=psusi@ubuntu.com \
    --cc=thomas-forum@orgis.org \
    --cc=util-linux@vger.kernel.org \
    --cc=vapier@gentoo.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