hey, On 10/08/2009 Stuart Pook wrote: > On 03/08/09 15:21, Jonas Meurer wrote: > > >I mean this: > >-ACTION!="add|change", GOTO="device_mapper_end" > >+ACTION!="change", GOTO="device_mapper_end" > > this change didn't help for me > > : root; /etc/init.d/udev restart > Stopping the hotplug events dispatcher: udevd. > Starting the hotplug events dispatcher: udevd. > : 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; grep change /etc/udev/rules.d/65_dmsetup.rules > ACTION!="change", GOTO="device_mapper_end" > : root; dpkg -s cryptsetup | grep -i version > Version: 2:1.0.7-1 > dm-crypt. This version of cryptsetup has integrated support for LUKS. > : root; apt-get -t testing install cryptsetup/testingReading package lists... > Done > The following packages will be DOWNGRADED: > cryptsetup > dpkg: warning: downgrading cryptsetup from 2:1.0.7-1 to > 2:1.0.6+20090405.svn49-1. > : root; dpkg -s cryptsetup | grep -i version > Version: 2:1.0.6+20090405.svn49-1 > dm-crypt. This version of cryptsetup has integrated support for LUKS. > : root; cryptsetup luksOpen /dev/mapper/vg0-services_var services_var > --key-file /tmp/xx > key slot 1 unlocked. > Command successful. > > Perhaps something else has to be done to reread the new > /etc/udev/rules.d/65_dmsetup.rules?
do you have any further information about the bug? are you still able to reproduce it? did the changed udev rules make any difference? in order to reproduce the bug it would be great if you could give more information about you system. which kernel do you run? is it a custom selfcompiled kernel? is your system up-to-date? what's the content of your /etc/crypttab and /etc/fstab? greetings, jonas
signature.asc
Description: Digital signature
