Comment # 47 on bug 902779 from Thomas Blume

Thanks for the feedback.

Just be aware that the enabled lvm2-lvmetad.socket is not a bug.
It is enabled by default and this is how it should be.

The real problem is that an lvm device scan is executed, even though you don't
have any lvm setup.
This device scan starts lvmetad via its socket and in turn lvmetad causes the
boot delay.
Normally, there should be no lvm device scan if there is no lvm setup.
In addition, there is acces to the lvmetad socket, even though lvm is not using
lvmetad (use_lvmetad=0 is set).
This shouldn't happen either.
I guess this behaviour is a leftover from previous tests with lvm and lvmetad
activated.
I couldn't reproduce it on a fresh clean factory install from 20150115.
Closing the bug therewith.