Comment 25 for bug 802626
Revision history for this message
| Ian Jackson (ijackson) wrote lvm hangs: watershed and environment | #25 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
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.
Ian.