Carlo Wood schrieb: > 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. Great, could you as well test if you get this problem when running multiple luksOpen/luksClose in a short period of time, like in my first posting in the other thread? It seems to me that you indeed have the same problem. Sadly, it appears that there is no interest from the dm-crypt/cryptsetup developers to fix this, or that none of them even reads this list. --------------------------------------------------------------------- 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
