From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mta-2.ms.rz.rwth-aachen.de (mta-2.ms.rz.RWTH-Aachen.DE [134.130.7.73]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Tue, 20 Oct 2009 10:35:06 +0200 (CEST) MIME-version: 1.0 Received: from ironport-out-1.rz.rwth-aachen.de ([134.130.5.40]) by mta-2.ms.rz.RWTH-Aachen.de (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008)) with ESMTP id <0KRT00HMG16IT650@mta-2.ms.rz.RWTH-Aachen.de> for dm-crypt@saout.de; Tue, 20 Oct 2009 10:35:06 +0200 (CEST) Received: from [134.61.47.76] ([unknown] [134.61.47.76]) by relay-auth-2.ms.rz.rwth-aachen.de (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 9 2008)) with ESMTPA id <0KRT005ZI16HDH60@relay-auth-2.ms.rz.rwth-aachen.de> for dm-crypt@saout.de; Tue, 20 Oct 2009 10:35:06 +0200 (CEST) Message-id: <4ADD7639.6060904@archlinux.org> Date: Tue, 20 Oct 2009 10:35:05 +0200 From: =?ISO-8859-15?Q?Thomas_B=E4chler?= Content-type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary=------------enig7FC94ECB4D77D57187D751C3 Subject: [dm-crypt] 1.1.0rc2: device-mapper: remove ioctl failed: Device or resource busy List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig7FC94ECB4D77D57187D751C3 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: quoted-printable Okay, this report has a long story. I had reports of cryptsetup 1.0.7 failing to work after updates (I later found out that the cause was installing devicekit). I advised the affected people to try the 1.1.0 release candidate to get better debug output - but the bug was gone with 1.1.0. But something else happened with 1.1.0: On every opened LUKS volume, the message device-mapper: remove ioctl failed: Device or resource busy would appear (see http://bugs.archlinux.org/task/16735#comment51508). Then I suggested adding the following udev rule (which I will probably make the default): ACTION=3D=3D"add|change", SUBSYSTEM=3D=3D"block", KERNEL=3D=3D"dm-[0-9]*"= , PROGRAM=3D"/sbin/dmsetup info -c --noopencount --noheadings -o name -j %M= -m %m", RESULT=3D=3D"temporary-cryptsetup-*", OPTIONS=3D"last_rule" (btw, is there a better way than calling dmsetup to get the name here?). Now, this fixes the problem with 1.0.7, as it prevents devicekit from blocking access to the device, but the above error message isn't gone in 1.1.0: http://bugs.archlinux.org/task/16735#comment51536 What is this remove error caused by, if not by some application being called from udev blocking access? Note that there are no temporary-cryptsetup-* volumes left after luksOpen. Ideas welcome :) --------------enig7FC94ECB4D77D57187D751C3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkrddjkACgkQEda5KzHP/VCi2QCfeQOEahFx94R3a6Oo1V6HG4nK DvsAn2T8Y3/ewMzzJlOMGhL092T88rMM =uryb -----END PGP SIGNATURE----- --------------enig7FC94ECB4D77D57187D751C3--