[Bug 802626] lvm hangs: watershed and environment
ijackson at chiark.greenend.org.uk
Tue Nov 8 12:04:17 UTC 2011
Another possible cause of problems is that, due to the use of
watershed, DM_COOKIE is not passed to the actual invocation of
vgchange, or vgchange is run fewer times than expected.
watershed considers two identical command lines with different
environments coalescable. So if you run
watershed vgchange -a y &
DM_COOKIE=A watershed vgchange -a y &
DM_COOKIE=B watershed vgchange -a y &
vgchange may see any subset (by DM_COOKIE setting) of the calls.
I don't know the innards of the lvm/udev plumbing well enough to know
if this is going to be a problem, but from the descriptions in this
bug it seems it might be.
Of course simply removing the use of watershed, or manually putting
the cookie in the watershed command-id (or on the watershed command
line, for the same effect), will with the current udev rules result in
lots of serialised invocations of vgscan.
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to udev in Ubuntu.
vgchange may deadlock in initramfs when VG present that's not used for
Status in “lvm2” package in Ubuntu:
Status in “udev” package in Ubuntu:
Status in “lvm2” source package in Oneiric:
Status in “udev” source package in Oneiric:
The system is now unable to boot.
I had to boot on previous kernel 3.0.0.
Symptoms are boot freezes. When debugging, issuing a vgscan works ok.
doing the vgchange -a y just hangs. I need to reboot the system afterwards.
DistroRelease: Ubuntu 11.10
Package: lvm2 2.02.66-4ubuntu2
ProcVersionSignature: Ubuntu 3.0-0.1-generic 3.0.0-rc2
Uname: Linux 3.0-0-generic x86_64
Date: Mon Jun 27 18:15:46 2011
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
More information about the foundations-bugs