I am booting a fully-encrypted system. When the genkernel-created startscripts in the initfs ask for the passhprase I get a warning, that udevadm is not available and thus race conditions cannot be avoided. This warning is printed by the cryptsetup binary. (cryptsetup version 1.0.6)
Steps to Reproduce:
1. add luks and lvm support to genkernel
2. boot an ancrypted system
/sbin/cryptsetup tries to execute "/sbin/udevadm settle" and
the following error message is triggered:
"%s unable to avoid potential race with busy device-mapper device"
no output at all ;)
The initramfs does not use udev, so including udevadm does not make sense. It uses mdev from busybox.
I think that a system shouldn't give you an errormessage at bootup when everything is working.
So by adding a dummy shellscript or a symlink to /bin/true would make the errormessage go away, although this is an ugly workaround. One could state, that at this stage there is only one process running and hope there is no race condition here.
Or cryptsetup needs a patch to use mdev in that case?
Same problem here. 2.6.28-tuxonice-r10, genkernel 126.96.36.1994, cryptsetup 1.0.6-r2.
I think this one belongs to base-system.
Also reproduced this bug. But severity is maybe minor.
i dropped the small hunk that added the complaint