[dm-crypt] The weird bug again: semid XXXXXX: semop failed for cookie 0xdeadbeef: incorrect semaphore state
corsac at debian.org
Wed Aug 17 12:43:14 CEST 2011
On mer., 2011-08-17 at 13:22 +0200, Alexander Koch wrote:
> [alex at thor ~]$ sudo vgchange -an ArchiveGroup
> 0 logical volume(s) in volume group "ArchiveGroup" now active
> semid 557056: semop failed for cookie 0xd4d88de: incorrect semaphore
> Failed to set a proper state for notification semaphore identified
> by cookie value 223185118 (0xd4d88de) to initialize waiting for incoming
vchange is only LVM, not dm-crypt, is it? So might not be related at all
to dm-crypt or cryptsetup?
For chromium, it might be that the default sandboxing (setuid one) uses
PID and network namespaces. Not sure why it'd mess with semaphores, but
maybe there's something to look at there.
More information about the dm-crypt