http://bugzilla.opensuse.org/show_bug.cgi?id=902779
--- Comment #46 from Sebastian Kuhne
(In reply to Sebastian Kuhne from comment #44)
use_lvmetad = 0 was already activated.
I have executed "systemctl disable lvm2-lvmetad.socket", and the output of journalctl -axb attached (udev_log="debug").
Sorry for this issue. Many thanks for your help!
Hm, still lvmetad was started:
--<-- Jan 19 09:05:04 linux-1r76 lvm[384]: WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it! -->--
This shouldn't happen if lvm2-lvmetad.service and lvm2-lvmetad.socket are disabled. The only possibility, I can think of, is that it was started in the initrd. Did you run mkinitrd after disabling lvm2-lvmetad.socket?
However, the boot times look ok now. kdm gets started after 21s:
-->-- Jan 19 09:04:58 linux-1r76 kernel: Linux version 3.16.7-7-desktop (geeko@buildhost) (gcc version 4.8.3 20140627 [gcc-4_8-branch revision 212064] (SUSE Linux) ) #1 SMP PREEMPT Wed Dec 17 18:00:44 UTC 2014 (762f27a) [...] Jan 19 09:05:19 linux-1r76 display-manager[652]: Starting service kdm..done --<--
Can you confirm that this fixes your issue?
Good morning, no I didn't run mkinitrd after disabling lvm2-lvmetad.socket. But, as you said, the boot time looks OK now. I can confirm that this fixes my issue. I'll keep lvm2-lvmetad.socket disabled. Thank you for your great support. Best regards, Sebastian -- You are receiving this mail because: You are on the CC list for the bug.