[pkg-cryptsetup-devel] Bug#601886: Bug#601886: cryptsetup: luksformat leaves the Luks device open

[Jonas Meurer]

Hey intrigeri,

On 30/10/2010 intrigeri at boum.org wrote:
> Hi,
> 
> 	# ls -l /dev/mapper/luksformat1 
> 	ls: cannot access /dev/mapper/luksformat1: No such file or directory
> 
> 	# luksformat /dev/sdb1
>         Creating encrypted device on /dev/sdb1...
> 
> 	WARNING!
> 	========
> 	This will overwrite data on /dev/sdb1 irrevocably.
> 	
> 	Are you sure? (Type uppercase yes): YES
> 	Enter LUKS passphrase: 
> 	Verify passphrase: 
> 	Please enter your passphrase again to verify it
> 	Enter passphrase for /dev/sdb1: 
> 	mkfs.vfat 3.0.9 (31 Jan 2010)
> 	unable to get drive geometry, using default 255/63
> 	
> 	Device luksformat1 is busy.
> 
> 	# ls -l /dev/mapper/luksformat1
> 	lrwxrwxrwx 1 root root 8 Oct 30 18:23 /dev/mapper/luksformat1 -> ../dm-11

mh, seems like another race condition. the device is still busy when
mkfs.vfat terminates. a workaround like sleep 1 in between would work,
but i would prefer to find the reason for this race condition and fix
it.

milan, maybe you could take a look at this? unfortunately i don't know
enough udev/devmapper details to further debug this issue.

but i guess that the race condition is between libdevmapper and udev.
maybe this is related to the outdated devmapper (+udev rules) in debian?

on irc someone said that cryptsetup (luksClose) should wait for the
device to become free in case that udev sync is enabled.

greetings,
 jonas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20110219/0dbbf96b/attachment.pgp>