Am 12.04.2010 14:51, schrieb Dieter Plaetinck:
There were a number of races w.r.t. device creating and linking in the past. You could try udevadm settle (maybe with a --subsystem= option) after cryptsetup as a workaround and see if the bug disappears. Other than that, I wouldn't know how to solve it.
or hell. sleep 10. Chris, feeling lucky? :)
Or that, at least for a short test.
Also, please make sure that all files (especially udev rules) from device-mapper are installed into /lib/udev/rules.d/ (they should be, as archiso uses pacman, but it never hurts to be absolutely sure).
okay. btw on my laptop (which uses a lvm-on-top-of-dm_crypt setup): dieter@dieter-dellD620-arch ~ ls /lib/udev/rules.d/*crypt* /lib/udev/rules.d/*mapp* ls: cannot access /lib/udev/rules.d/*crypt*: No such file or directory ls: cannot access /lib/udev/rules.d/*mapp*: No such file or directory
? Dieter
$ ls -lhF /lib/udev/rules.d/*dm* /sbin/dmsetup -rw-r--r-- 1 root root 4,4K 6. Apr 05:55 /lib/udev/rules.d/10-dm.rules -rw-r--r-- 1 root root 1,3K 6. Apr 05:55 /lib/udev/rules.d/11-dm-lvm.rules -rw-r--r-- 1 root root 1011 6. Apr 05:55 /lib/udev/rules.d/13-dm-disk.rules -rw-r--r-- 1 root root 492 6. Apr 05:55 /lib/udev/rules.d/95-dm-notify.rules -r-xr-xr-x 1 root root 53K 6. Apr 05:55 /sbin/dmsetup*