All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Orgis <thomas-forum@orgis.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: util-linux@vger.kernel.org
Subject: Re: losetup -d --force for zombie loop devices?
Date: Tue, 17 Apr 2012 23:02:07 +0200	[thread overview]
Message-ID: <20120417230207.352c4ca5@orgis.org> (raw)
In-Reply-To: <201204171058.23776.vapier@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 599 bytes --]

Am Tue, 17 Apr 2012 10:58:22 -0400
schrieb Mike Frysinger <vapier@gentoo.org>: 

> that's LOOP_CLR_FD returning EBUSY.  so there isn't much (afaik) that 
> userspace can do here.  you'd have to start a thread on lkml first to add 
> support for lazy/force loop device detaching.

Hm, I feared such ... now the question is if folks would support that
move. Well, one will not find out without asking. Perhaps I should try
to reproduce the scheme with another machine first. Not that this
situation is something that "just does not happen", except in my case.


Alrighty then,

Thomas

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2012-04-17 21:02 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 [this message]
2012-04-30 20:03 ` Phillip Susi
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=20120417230207.352c4ca5@orgis.org \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.