On Mon, Jun 18, 2007 at 08:20:55PM +0200, Thomas Bächler wrote: > Carlo Wood schrieb: > > Linux hikaru 2.6.22-rc4-hikaru-amd64 #1 SMP Fri Jun 15 00:34:35 CEST 2007 x86_64 GNU/Linux > > > > Debian testing, with a self-compiled kernel (though the configuration > > is the same as from the debian trunk kernel). > > Thanks. So far I only found Archlinux users with the problem, now I know > there is someone with a completely different system. > > As written in the other thread, my problem (which I only experienced > with luksOpen and luksAddKey so far), results from a failed ioctl, can > you strace your cryptsetup and see if you get this: > > ioctl(3, DM_DEV_CREATE, 0xdeadbeef) = -1 EBUSY (Device or resource busy) I get, indeed at random, both ioctl(3, DM_DEV_REMOVE, 0x564ae0) = -1 EBUSY (Device or resource busy) and ioctl(3, DM_DEV_CREATE, 0x569d70) = -1 EBUSY (Device or resource busy) while, in those cases that the luksAddKey (or luksDelKey) DOES succeed, no EBUSY is present. -- Carlo Wood <carlo@xxxxxxxxxx> --------------------------------------------------------------------- dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
