I'm seeing these semaphore errors with a backup-script that uses lvm2 snapshots after upgrading to natty.
I think this bug should be reopened and moved to the proper package (lvm2?) and it should probably be merged with bug #753541 May 9 21:21:43 sphere udevd-work[5144]: inotify_add_watch(6, /dev/dm-25, 10) failed: No such file or directory May 9 21:21:47 sphere udevd-work[5144]: inotify_add_watch(6, /dev/dm-22, 10) failed: No such file or directory May 9 21:21:51 sphere udevd-work[5144]: inotify_add_watch(6, /dev/dm-19, 10) failed: No such file or directory May 9 21:21:54 sphere udevd-work[5144]: inotify_add_watch(6, /dev/dm-28, 10) failed: No such file or directory May 9 21:21:58 sphere udevd-work[5144]: inotify_add_watch(6, /dev/dm-31, 10) failed: No such file or directory May 9 21:22:02 sphere udevd-work[5144]: inotify_add_watch(6, /dev/dm-16, 10) failed: No such file or directory May 9 21:22:05 sphere udevd-work[5144]: inotify_add_watch(6, /dev/dm-13, 10) failed: No such file or directory semid 1179650: semop failed for cookie 0xd4d8346: incorrect semaphore state Could not signal waiting process using notification semaphore identified by cookie value 223183686 (0xd4d8346) semid 1179650: semop failed for cookie 0xd4d8346: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223183686 (0xd4d8346) to initialize waiting for incoming notifications. semid 1245186: semop failed for cookie 0xd4d7e40: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223182400 (0xd4d7e40) to initialize waiting for incoming notifications. semid 1277954: semop failed for cookie 0xd4d59e4: incorrect semaphore state Could not signal waiting process using notification semaphore identified by cookie value 223173092 (0xd4d59e4) semid 1277954: semop failed for cookie 0xd4d59e4: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223173092 (0xd4d59e4) to initialize waiting for incoming notifications. semid 1343490: semop failed for cookie 0xd4d451a: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223167770 (0xd4d451a) to initialize waiting for incoming notifications. semid 1376258: semop failed for cookie 0xd4dc3e3: incorrect semaphore state Could not signal waiting process using notification semaphore identified by cookie value 223200227 (0xd4dc3e3) semid 1376258: semop failed for cookie 0xd4dc3e3: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223200227 (0xd4dc3e3) to initialize waiting for incoming notifications. semid 1441794: semop failed for cookie 0xd4dd615: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223204885 (0xd4dd615) to initialize waiting for incoming notifications. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/719388 Title: semop failed for cookie 0xd4d09ef: incorrect semaphore state during luksOpen -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
