Most time (but not everytime) when i call cryptdisks_start it reports: #cryptdisks_start extern0 Starting crypto disk...extern0 (starting)... semid 2293761: semop failed for cookie 0xd4d580e: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223172622 (0xd4d580e) to initialize waiting for incoming notifications. The node /dev/mapper/extern0_unformatted should have been renamed to /dev/mapper/extern0 by udev but new node is not present. Falling back to direct node rename. extern0 (started)...done. I made checks every startup of the disk but there are no errors on it. Is the "semop failed" a real problem or only a information? System: debian-sid Linux 2.6.35-trunk-amd64 hard dirve, on top lvm, on top dmcrypt/luks(using aes-xts-plain 64) with ext4 file system Version: cryptsetup 1.1.3 Best Regards, Benno _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
