lvm schroots 'not created with udev' error messages

[James Page]

Binary package hint: schroot

All of my schroot environments are setup on lvm for the last five distributions.

When I enter a schroot environment I get the following message:

E: 05lvm: The link /dev/hendrix/natty-dev-amd64-064e4c17-ac7a-4d3a-a010-2778541e2976 should had been created by udev but it was not found. Falling back to direct link creation.
E: 05lvm: semid 2260994: semop failed for cookie 0xd4d6813: incorrect semaphore state
E: 05lvm: Failed to set a proper state for notification semaphore identified by cookie value 223176723 (0xd4d6813) to initialize waiting

and when I exit a similar message:

E: 05lvm: semid 2326530: semop failed for cookie 0xd4ddbb6: incorrect semaphore state
E: 05lvm: Could not signal waiting process using notification semaphore identified by cookie value 223206326 (0xd4ddbb6)
E: 05lvm: semid 2326530: semop failed for cookie 0xd4ddbb6: incorrect semaphore state
E: 05lvm: Failed to set a proper state for notification semaphore identified by cookie value 223206326 (0xd4ddbb6) to initialize waiting

The session appears to cleanup OK.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: schroot 1.4.17-1
ProcVersionSignature: Ubuntu 2.6.38-8.40-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Thu Apr 7 14:30:14 2011
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: schroot
UpgradeStatus: Upgraded to natty on 2011-04-06 (1 days ago)

[Randall Leeds (randall-leeds)]

From debbugs thread, changelog for udev 163-1: "Since lvm still has not been fixed, revert the change from 161-1 and delete again the udev database created by the initramfs udev."

Marking this against udev, but maybe it's also related to a different bug or obsoleted by a different bug on lvm2 as well.

[Randall Leeds (randall-leeds)]

The "workaround" in the debian bug report doesn't seem to apply: udev in ubuntu has been converted to an upstart job and I don't see any script that rm's the /failed directory. I must admit I'm a bit afraid to nuke /dev/.udev/ so I can't test what happens if I try.

[Linus van Geuns (nirkus)]

Not fixed, see post #15 on bug #719388.
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/719388/comments/15

[Roger Leigh (rleigh)]

While schroot uses lvcreate/lvremove, it is not itself responsible for any lvm issues. This is not a schroot bug, and should be reassigned to lvm2/dmsetup/udev as appropriate.

Also, is this still reproducible, or is it fixed with new upstream versions of the above?

[Randall Leeds (randall-leeds)]

Not reproducible for me on an up to date precise.

[Reinhard Tartler (siretart)]

I'm closing this bug based on the unanswered question #5 and comment #6.
Feel free to reopen with additional information, though!

[Roger Leigh (rleigh)]

I've not yet seen any evidence that the underlying LVM issues have been fixed, so I am not fully convinced that this is yet resolved.