On 04/27/2010 10:56 PM, Douglas McClendon wrote: > zyx-liveinstaller-cli: creating temporary rootfs virtual duplicate > device-mapper: resume ioctl failed: Invalid argument > semid 65536: semop failed for cookie 0xd4d423c: incorrect semaphore state > Failed to set a proper state for notification semaphore identified by > cookie value 223167036 (0xd4d423c) to initialize waiting for incoming > notifications. Well, the primary cause is that "resume" ioctl that is failing (can you trace the exact parameters that are substituted in the script for that failing dmsetup call?). I think the errors printed afterwards are just an outcome of this failure. Anyway, it seems that our internal "_udev_complete" fn is called more than once on some error path. This call is exactly the same as calling "dmsetup udevcomplete", but we have to call one internally if any error occurs while processing a device-mapper task (that generates udev events). That's because we can't await any notification for failed ioctls since no udev events will be generated. We need to do that to prevent infinite waiting for notifications that will never come. If that internal _udev_complete is called more than necessary, we'll get into an improper state with the semaphore so that needs to be fixed! What's the exact version of dmsetup/lvm2 used? Also, in addition to Alasdair's hints in the other post, could you please run the failing dmsetup with verbose output "dmsetup -vv ...". This way we should see how the semaphore is handled throughout processing.. Peter -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
