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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/802626 Title: vgchange may deadlock in initramfs when VG present that's not used for rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/802626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
