Bug#728486: Current patch for resolving lvm/systemd compatibility
Bastian Blank wrote:
>On Sat, Jan 18, 2014 at 11:33:32PM +0100, Michael Biebl wrote:
>> Wants= will make sure the systemd-udev-settle.service is started
>> dynamically and After= ensures the correct ordering.
>
> It only makes sure that systemd-udev-settle.service was started
> somewhere _before_. It does however not make sure it is called again
> for the second round or third round.
It doesn't matter if you run "udevadm settle" once, twice, or twelve
times; it still won't guarantee that more devices won't show up later.
Dynamic hardware detection does not work the way you wish it did, and
"udevadm settle" will not change that; it will only slow down the boot
process for everyone. Calling it once for all broken services is quite
enough.
On a different note, this patch also has a serious limitation: it
doesn't automatically disable itself when use_lvmetad=1, which seems
like the right way to handle dynamic hardware detection in any
environment that lvmetad can handle (anything other than a multi-host
cluster, as far as I can tell).
- Josh Triplett
Reply to: