Bug#538221: [pkg-cryptsetup-devel] Bug#538221: cryptsetup: Command failed: device-mapper: create ioctl failed: Device or resource busy

2009-08-04 Thread Jonas Meurer
On 03/08/2009 Stuart Pook wrote:
 hello Jonas
 
 Jonas Meurer wrote:
  please also provide the output of 'udevadm monitor' while running
  'cryptsetup luksOpen ...'.
 
 I guess that you don't need this anymore given that you have found the
 bad rule in udev

hey,

maybe you could check whether the proposed change from Milan Broz fixes
your issues.

greetings,
 jonas


signature.asc
Description: Digital signature


Bug#538221: Info received ([pkg-cryptsetup-devel] Bug#538221: cryptsetup: Command failed: device-mapper: create ioctl failed: Device or resource busy)

2009-08-03 Thread Stuart Pook
this was reported upstream 
http://code.google.com/p/cryptsetup/issues/detail?id=34



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#538221: [pkg-cryptsetup-devel] Bug#538221: cryptsetup: Command failed: device-mapper: create ioctl failed: Device or resource busy

2009-08-03 Thread Jonas Meurer
hey,

On 02/08/2009 Stuart Pook wrote:
 On 31/07/09 01:58, Jonas Meurer wrote:
 this sounds like a udev race condition. could you give cryptsetup
 2:1.0.7-1 from debian/unstable a try?
 
 2:1.0.7-1 does not work either
 
 : root; cryptsetup luksOpen /dev/mapper/vg0-asterisk_ROOT_snapshot 
 asterisk_ROOT_snapshot --key-file /tmp/xx
 key slot 0 unlocked.
 Command failed: device-mapper: create ioctl failed: Device or resource busy

do you have any custom udev rules set? upstream shares my assumption
that your issue is caused by a udev race. we're both unable to reproduce
the bug on our systems.

please also provide the output of 'udevadm monitor' while running
'cryptsetup luksOpen ...'.

greetings,
 jonas


signature.asc
Description: Digital signature


Bug#538221: [pkg-cryptsetup-devel] Bug#538221: cryptsetup: Command failed: device-mapper: create ioctl failed: Device or resource busy

2009-08-02 Thread Stuart Pook

hi Jonas

On 31/07/09 01:58, Jonas Meurer wrote:

this sounds like a udev race condition. could you give cryptsetup
2:1.0.7-1 from debian/unstable a try?


2:1.0.7-1 does not work either

: root; cryptsetup luksOpen /dev/mapper/vg0-asterisk_ROOT_snapshot 
asterisk_ROOT_snapshot --key-file /tmp/xx
key slot 0 unlocked.
Command failed: device-mapper: create ioctl failed: Device or resource busy
: root; cryptsetup luksOpen /dev/mapper/vg0-asterisk_ROOT_snapshot 
asterisk_ROOT_snapshot --key-file /tmp/xx
key slot 0 unlocked.
Command failed: device-mapper: create ioctl failed: Device or resource busy
: root; cryptsetup luksOpen /dev/mapper/vg0-asterisk_ROOT_snapshot 
asterisk_ROOT_snapshot --key-file /tmp/xx
key slot 0 unlocked.
Command failed: device-mapper: create ioctl failed: Device or resource busy
: root; dpkg -s cryptsetup | grep Version
Version: 2:1.0.7-1
: root; cryptsetup luksOpen /dev/mapper/vg0-asterisk_ROOT_snapshot 
asterisk_ROOT_snapshot --key-file /tmp/xx
key slot 0 unlocked.
Command failed: device-mapper: create ioctl failed: Device or resource busy
: root; strace -o /tmp/cryptsetup.output  cryptsetup luksOpen 
/dev/mapper/vg0-asterisk_ROOT_snapshot asterisk_ROOT_snapshot --key-file /tmp/xx
key slot 0 unlocked.
Command failed: device-mapper: create ioctl failed: Device or resource busy
: root; strace -f -o /tmp/cryptsetup.output2  cryptsetup luksOpen 
/dev/mapper/vg0-asterisk_ROOT_snapshot asterisk_ROOT_snapshot --key-file /tmp/xx
key slot 0 unlocked.
Command failed: device-mapper: create ioctl failed: Device or resource busy
: root; cryptsetup luksOpen /dev/mapper/vg0-asterisk_ROOT_snapshot 
asterisk_ROOT_snapshot --key-file /tmp/xx
key slot 0 unlocked.
Command failed: device-mapper: create ioctl failed: Device or resource busy
: root; apt-get -t testing install cryptsetup/testing
Reading package lists... Done
Building dependency tree   
Reading state information... Done

Selected version 2:1.0.6+20090405.svn49-1 (Debian:testing) for cryptsetup
The following packages will be DOWNGRADED:
 cryptsetup
0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 71 not upgraded.
Need to get 0B/331kB of archives.
After this operation, 8192B disk space will be freed.
Do you want to continue [Y/n]? y
dpkg: warning: downgrading cryptsetup from 2:1.0.7-1 to 
2:1.0.6+20090405.svn49-1.
(Reading database ... 250249 files and directories currently installed.)
Preparing to replace cryptsetup 2:1.0.7-1 (using 
.../cryptsetup_2%3a1.0.6+20090405.svn49-1_i386.deb) ...
Unpacking replacement cryptsetup ...
Processing triggers for man-db ...
Setting up cryptsetup (2:1.0.6+20090405.svn49-1) ...
Installing new version of config file /etc/init.d/cryptdisks-early ...
Installing new version of config file /etc/init.d/cryptdisks ...
Installing new version of config file /etc/bash_completion.d/cryptsetup ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.30-1-686
localepurge: Disk space freed in /usr/share/locale: 12K
: root; cryptsetup luksOpen /dev/mapper/vg0-asterisk_ROOT_snapshot 
asterisk_ROOT_snapshot --key-file /tmp/xx
key slot 0 unlocked.
Command successful.



and in case that you're still able
to reproduce the bug, please provide the output of 'strace cryptsetup
luksOpen ...'.


I will email them to you (because they might contain sensitive information).

Stuart



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#538221: [pkg-cryptsetup-devel] Bug#538221: cryptsetup: Command failed: device-mapper: create ioctl failed: Device or resource busy

2009-07-30 Thread Jonas Meurer
Hey Stuart,

thanks for your bugreport.

On 24/07/2009 Stuart Pook wrote:
 Crytsetup 2:1.0.7~rc1-2 often fails to open my devices. Sometimes it works 
 but I'm not exactly sure under
 what conditions. Downgrading to 2:1.0.6+20090405.svn49-1 from testing works.
 
 : root; cryptsetup luksOpen /dev/mapper/vg0-services_var services_var 
 --key-file /tmp/xx
 key slot 1 unlocked.
 Command failed: device-mapper: create ioctl failed: Device or resource busy
 : root; apt-get -t testing install cryptsetup/testing

this sounds like a udev race condition. could you give cryptsetup
2:1.0.7-1 from debian/unstable a try? and in case that you're still able
to reproduce the bug, please provide the output of 'strace cryptsetup
luksOpen ...'.

greetings,
 jonas


signature.asc
Description: Digital signature


Bug#538221: cryptsetup: Command failed: device-mapper: create ioctl failed: Device or resource busy

2009-07-24 Thread Stuart Pook
Package: cryptsetup
Version: 2:1.0.7~rc1-2
Severity: important

Crytsetup 2:1.0.7~rc1-2 often fails to open my devices. Sometimes it works but 
I'm not exactly sure under
what conditions. Downgrading to 2:1.0.6+20090405.svn49-1 from testing works.

: root; cryptsetup luksOpen /dev/mapper/vg0-services_var services_var 
--key-file /tmp/xx
key slot 1 unlocked.
Command failed: device-mapper: create ioctl failed: Device or resource busy
: root; apt-get -t testing install cryptsetup/testing
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Selected version 2:1.0.6+20090405.svn49-1 (Debian:testing) for cryptsetup
The following packages will be DOWNGRADED:
  cryptsetup
0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 3 not upgraded.
Need to get 0B/331kB of archives.
After this operation, 4096B disk space will be freed.
Do you want to continue [Y/n]? 
dpkg: warning: downgrading cryptsetup from 2:1.0.7~rc1-2 to 
2:1.0.6+20090405.svn49-1.
(Reading database ... 250248 files and directories currently installed.)
Preparing to replace cryptsetup 2:1.0.7~rc1-2 (using 
.../cryptsetup_2%3a1.0.6+20090405.svn49-1_i386.deb) ...
Unpacking replacement cryptsetup ...
Processing triggers for man-db ...
Setting up cryptsetup (2:1.0.6+20090405.svn49-1) ...
Installing new version of config file /etc/init.d/cryptdisks-early ...
Installing new version of config file /etc/init.d/cryptdisks ...
Installing new version of config file /etc/bash_completion.d/cryptsetup ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.30-1-686
localepurge: Disk space freed in /usr/share/locale: 12K
: root; cryptsetup luksOpen /dev/mapper/vg0-services_var services_var 
--key-file /tmp/xx
key slot 1 unlocked.
Command successful.



-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages cryptsetup depends on:
ii  dmsetup  2:1.02.30-3 The Linux Kernel Device Mapper use
ii  libc62.9-21  GNU C Library: Shared libraries
ii  libdevmapper1.02.1   2:1.02.30-3 The Linux Kernel Device Mapper use
ii  libpopt0 1.14-4  lib for parsing cmdline parameters
ii  libuuid1 1.41.8-2Universally Unique ID library

cryptsetup recommends no packages.

Versions of packages cryptsetup suggests:
ii  dosfstools3.0.4-1utilities for making and checking 
ii  initramfs-tools [linux-initra 0.93.3 tools for generating an initramfs
ii  udev  0.141-1/dev/ and hotplug management daemo

-- debconf-show failed



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org