From: "Thomas Bächler" <thomas@archlinux.org>
To: Peter Rajnoha <prajnoha@redhat.com>
Cc: dm-crypt@saout.de, Milan Broz <mbroz@redhat.com>
Subject: Re: [dm-crypt] 1.1.0rc2: device-mapper: remove ioctl failed: Device or resource busy
Date: Thu, 22 Oct 2009 17:01:49 +0200 [thread overview]
Message-ID: <4AE073DD.9070903@archlinux.org> (raw)
In-Reply-To: <4AE05FE8.7090908@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 609 bytes --]
Peter Rajnoha schrieb:
> ..ok, finally we kept the "last_rule" in the lvm/dm upstream. This is the
> safe way. Maybe later we can think of a solution where we will rely on the
> others so they will check the variables we set for them (if that's
> possible at all). But it would be too dangerous now, I have to admit.
>
> You can check the rules we have in the upstream - if you have any comments
> or hints, just feel free to write me back...
I am going to replace our own device-mapper rules with upstream rules (I
think when we made our own rules, dm didn't have any, or I overlooked them).
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]
next prev parent reply other threads:[~2009-10-22 15:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 8:35 [dm-crypt] 1.1.0rc2: device-mapper: remove ioctl failed: Device or resource busy Thomas Bächler
2009-10-20 8:55 ` Milan Broz
2009-10-20 9:07 ` Thomas Bächler
[not found] ` <4ADD9876.8000006@redhat.com>
2009-10-20 12:13 ` Thomas Bächler
2009-10-20 12:53 ` Peter Rajnoha
2009-10-20 13:05 ` Thomas Bächler
2009-10-20 13:29 ` Peter Rajnoha
2009-10-22 13:36 ` Peter Rajnoha
2009-10-22 15:01 ` Thomas Bächler [this message]
2009-10-22 15:31 ` Peter Rajnoha
2009-10-23 13:41 ` Uwe Menges
2009-10-23 13:57 ` Milan Broz
-- strict thread matches above, loose matches on Subject: below --
2009-10-20 7:29 Thomas Bächler
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=4AE073DD.9070903@archlinux.org \
--to=thomas@archlinux.org \
--cc=dm-crypt@saout.de \
--cc=mbroz@redhat.com \
--cc=prajnoha@redhat.com \
/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