Quoting Kees Cook (k...@ubuntu.com): > On Fri, Sep 23, 2011 at 11:23:33PM -0000, Serge Hallyn wrote: > > Does that make any sense? It might mess up the use off watershed > > though. > > watershed is there to keep multiple invocations of effectively the same > event in check. For example, each time a pv appears, we attempt to activate > all VGs. But if all the drives suddenly appear at once, we only need > to attempt the activation once. (See the extensive comments at the start of > watershed.c in the watershed package.) > > It might be interesting to see if races are solved (or introduced) by > having watershed itself offer a "daemonize" option to put itself in the > background and immediately return to the caller (udev). This may solve it.
I'll try that out second, but > On the other hand, perhaps the solution is to fix up the udev rule to only > apply to PVs, and nothing else, as it certainly wasn't designed to run when > creating an LV. Ah, thanks, I didn't realize that. I can try that out. thanks, -serge -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/833891 Title: lvscan often times out during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/833891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
