Hi Marco, On Wed, Mar 14, 2012 at 11:19:22PM +0100, Marco d'Itri wrote: > reassign 663931 lvm2 > thanks > > On Mar 14, Ernesto Domato <[email protected]> wrote: > > > (about 3 minutes). Then I found running libvirtd on debug mode that it calls > > "udevadm settle" on startup. This command also takes about 3 minutes to > > respond. > Why does libvirtd run "udevadm settle", for a start? > > > Not using LVM doesn't generates this problem. > > > > So, it seems that when libvirtd is started and there's a pool that use LVM > > it > > mess with udev somehow that produce this behavior. > So this looks like a LVM issue. > It is not a udev bug unless you can show that it is.
There are several places in the code that try to make sure device nodes of newly plugged devices, created LVs, etc. are already there. Is there something better than doing a "udevadm settle"? Cheers, -- Guido -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
