[pkg-cryptsetup-devel] Bug#538221: [codesite-noreply at google.com: Issue 34 in cryptsetup: Command failed: device-mapper: create ioctl failed: Device or resource busy]

[Jonas Meurer]

reassign 538221 udev
thanks

I reassign this bug to udev as suggested by cryptsetup upstream Milan
Broz. 

Marco, a proposed fix is included in Milans response (see below).

greetings,
 jonas

----- Forwarded message from codesite-noreply at google.com -----

Date: Mon, 03 Aug 2009 13:12:54 +0000
From: codesite-noreply at google.com
To: jonas at freesources.org
Subject: Issue 34 in cryptsetup: Command failed: device-mapper: create ioctl
	failed: Device or resource busy

Updates:
	Status: Invalid
	Owner: gmazyland

Comment #4 on issue 34 by gmazyland: Command failed: device-mapper:
create ioctl failed: Device or resource busy
http://code.google.com/p/cryptsetup/issues/detail?id=34

Please report bug to udev rules in Debian:

Rule
  /etc/udev/rules.d/65_dmsetup.rules

is wrong, it runs dmsetup and vol_id on every appeared device. These
commands
unexpectedly locks the device.

This rule must break system in many other situations - nobody should
scan dm devices
in the middle of e.g. lvm operation (it can cause deadlock if device
is suspended).

You can temporary remove "add" from this rule and keep only "change"
event ("add" is
irrelevant for DM devices - change announces availability of mapping
anyway.)

I mean this:
-ACTION!="add|change",                           GOTO="device_mapper_end"
+ACTION!="change",                               GOTO="device_mapper_end"

FYI: there will be very soon upstream libdevmapper which will use udev
to create
device nodes with own udev rules.

This is completely Debian udev only problem not related with upstream
cryptsetup,
closing.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings


----- End forwarded message -----