From: Phillip Susi <psusi@ubuntu.com>
To: Thomas Orgis <thomas-forum@orgis.org>
Cc: util-linux@vger.kernel.org
Subject: Re: losetup -d --force for zombie loop devices?
Date: Mon, 30 Apr 2012 16:03:39 -0400 [thread overview]
Message-ID: <4F9EF01B.9040003@ubuntu.com> (raw)
In-Reply-To: <20120417100346.2a0b8301@orgis.org>
On 4/17/2012 4:03 AM, Thomas Orgis wrote:
> Hi,
>
> I am having an issue with a loop device that used to be connected to a file on NFS.
> Not sure if this is actually a kernel bug, but I assume (perhaps ignorantly so)
> that losetup could resolve the situation anyways.
>
> 0. have NFS share on /mnt/nfs (rw,users,noexec,nosuid,nodev,hard,intr)
> 1. losetup --show -f /mnt/nfs/file.img
> /dev/loop0
> # actually, it was using cryptsetup luksOpen/Close
> 2. mount /dev/loop0&& do_work&& umount /dev/loop0
> 3. loose connection to NFS server (it went offline, client machine (laptop) switched networks ...)
> 4. umount -l /mnt/nfs
This is the problem with umount -l: all it does is remove the path from
the namespace, leaving the device still mounted. Unfortunately umount
-f is not properly supported. The proper fix for this is to have the
kernel support umount -f, and do away with the brain damaged umount -l.
next prev parent reply other threads:[~2012-04-30 20:03 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 [this message]
2012-04-30 20:07 ` Mike Frysinger
2012-05-01 15:23 ` Phillip Susi
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=4F9EF01B.9040003@ubuntu.com \
--to=psusi@ubuntu.com \
--cc=thomas-forum@orgis.org \
--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