Mailinglist Archive: opensuse-bugs (4247 mails)

< Previous Next >
[Bug 1019886] Upgrade from 42.1 to 42.2 fails to initialize LVM VG with use_lvmetad = 1
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 17 Jan 2017 19:22:13 +0000
  • Message-id: <bug-1019886-21960-mnvScQjhM9@http.bugzilla.suse.com/>
http://bugzilla.suse.com/show_bug.cgi?id=1019886
http://bugzilla.suse.com/show_bug.cgi?id=1019886#c13

--- Comment #13 from Youri Matthys <youri@xxxxxxxxxx> ---
(In reply to zhen ren from comment #12)
Thanks for your confirmation. Following your steps, I failed to reproduce
this issue on my side. Everything works well after upgraded to Leap42.2. The
difference is my setup doesn't use md raid.

I will continue to try lvm2 on top of md-raid setup.

My pleasure.

As noted the parameter "use_lvmetad = 1" seems to require (in my specific case)
LVM modules included in the initrd. Setting this parameter to 0 "solves" the
issue on my system.

Could I propose adding the dracut rule for LVM by default to avoid issues in
the future whenever any VG is detected? Maybe we could even have the default
lvm.conf set to use_lvmetad = 0 by default?

It appears this issue is related to some upstream reports:
https://bbs.archlinux.org/viewtopic.php?id=173424
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774082

Thanks for your feedback. Let me know if I can assist further.

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >