https://bugzilla.novell.com/show_bug.cgi?id=854413 https://bugzilla.novell.com/show_bug.cgi?id=854413#c1 --- Comment #1 from Robert Milasan 2013-12-09 09:05:58 UTC --- Here is an example of the issue: rmilasan@coolcat:~> systemd-analyze blame|head 1.890s systemd-udev-settle.service 1.804s NetworkManager.service 1.447s ModemManager.service and if we check if 'systemd-analyze dump' we will see the both lvm2-activation-*.service file pull in systemd-udev-settle.service -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=854413 https://bugzilla.novell.com/show_bug.cgi?id=854413#c3 --- Comment #3 from Robert Milasan 2013-12-09 09:43:13 UTC --- Hannes, I wasn't referring to use vgscan, I was refering to use some kind of code similar to vgscan and patch lvm2-activation-generator to check itself if we do have VGs or lvm setup on the system and only then generate the service files. Also, there is no udev involved in this, only systemd. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=854413 https://bugzilla.novell.com/show_bug.cgi?id=854413#c5 --- Comment #5 from Robert Milasan 2013-12-09 10:36:30 UTC --- Maybe we should use what Archlinux does: http://lists.freedesktop.org/archives/systemd-devel/2013-December/015181.htm... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=854413 https://bugzilla.novell.com/show_bug.cgi?id=854413#c7 --- Comment #7 from Robert Milasan 2013-12-09 14:44:02 UTC --- Actually, after doing a test install of 13.1, I've found that we do have that setup has Archlinux has, but we also do have the lvm2-activation-generator. So I guess we can drop or we should drop lvm2-activation-generator, and we are done. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=854413 https://bugzilla.novell.com/show_bug.cgi?id=854413#c9 dong mao zhang changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|dmzhang@suse.com | --- Comment #9 from dong mao zhang 2013-12-10 19:17:08 HKT --- (In reply to comment #7)

Actually, after doing a test install of 13.1, I've found that we do have that setup has Archlinux has, but we also do have the lvm2-activation-generator.

So I guess we can drop or we should drop lvm2-activation-generator, and we are done.

If lvm user want to use lvmetad, I think they could drop lvm2-activation-generator. But if someone sets lvmetad=0 in lvm.conf, and he does not have the activation-generator, Does it mean he can not activate any LVM at boot time? I have not test this. If so, I think we should add this to the docs. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=854413 https://bugzilla.novell.com/show_bug.cgi?id=854413#c11 dong mao zhang changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xli@suse.com --- Comment #11 from dong mao zhang 2013-12-10 20:00:30 HKT --- I prefer setting lvmetad=1 as default for the normal users, but still keep activation-generator for cluster users. looking at this(https://bugzilla.redhat.com/show_bug.cgi?id=814779), lvmetad could not work in cluster environment. If a lvm user who has both local and cluster LV, the lock type will be 3. lvmetad can not work when lock type is 3. we still need the generator to activate the local LV. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=854413 https://bugzilla.novell.com/show_bug.cgi?id=854413#c13 dong mao zhang changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|dmzhang@suse.com | --- Comment #13 from dong mao zhang 2014-01-06 16:56:08 HKT --- (In reply to comment #12)

(In reply to comment #11)

How difficult would it be to let lvm2-activation-generator scan the lvm.conf for lvmetad=0 that ist that the lvm2-activation-generator does its job if required and otherwise simply does nothing?

lvm2-activation-generator is surely doing in this way. scan lvmetad = 1, if so, it just quit. If lvmetad = 0, it will generate a new service file which may cause the bootup slow. So setting lvmetad = 1 could resolve this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=854413 https://bugzilla.novell.com/show_bug.cgi?id=854413#c15 dong mao zhang changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|dmzhang@suse.com | Severity|Major |Critical --- Comment #15 from dong mao zhang 2014-01-08 00:18:50 HKT --- (In reply to comment #14)

(In reply to comment #13)

Hmmm ... OK, then the question rises: How the decision / Who has done the decision not to set `lvmetad = 1' for the reported system?

Is this done by YaST2 storage module or has the system administrator do this at his own?

YaST2 storage can not set lvmetad. But sysadmin could choose to set lvmetad=1. I was me who decided to make 'lvmetad = 0' because I want to put this as a new feature of LVM. If sysadmin really needs this, he could open it by himself. But it now appears "using lvmetad" is a better choice for normal users. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=854413 https://bugzilla.novell.com/show_bug.cgi?id=854413#c17 Raymond Wooninck changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tittiatcoke@gmail.com --- Comment #17 from Raymond Wooninck 2014-01-22 19:53:38 UTC --- Be aware that the latest changes to LVM2 (as in Base:System) causes huge issues in conjunction with grub2 (os-prober) and systemd during shutdown. In both cases the system hangs and will not continue. This could lead to corruption for configuration files, etc. I am not sure if the change indicated in this bug is the root cause, as that there are also other changes. But at least the main people are assigned to this bug. See also my email to the opensuse-factory mailinglist. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=854413 https://bugzilla.novell.com/show_bug.cgi?id=854413#c19 --- Comment #19 from Benjamin Brunner 2014-01-27 17:07:40 CET --- Ping? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=854413 https://bugzilla.novell.com/show_bug.cgi?id=854413#c22 Andrey Borzenkov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arvidjaar@gmail.com --- Comment #22 from Swamp Workflow Management 2014-02-03 15:35:59 UTC --- openSUSE-RU-2014:0186-1: An update that has 5 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 779965,837954,851741,854076,854413 CVE References: Sources used: openSUSE 13.1 (src): lvm2-2.02.98-0.28.5.1 --- Comment #23 from Andrey Borzenkov 2014-02-04 13:09:51 UTC --- (In reply to comment #15)

But it now appears "using lvmetad" is a better choice for normal users.

Looks like normal users have problems with it ... https://forums.opensuse.org/showthread.php/495141-boot-problem-after-lvm2-up... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=854413 https://bugzilla.novell.com/show_bug.cgi?id=854413#c25 --- Comment #25 from Andrey Borzenkov 2014-02-05 17:37:31 UTC --- Having lvmetad activated by default results in one cosmetic issue (bnc#862405) and one serious regression due to probing non-exiting floppy by default (bnc#862403). At least the latter should better be resolved before next version of this update is issued. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=854413 https://bugzilla.novell.com/show_bug.cgi?id=854413#c27 Benjamin Brunner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #27 from Benjamin Brunner 2014-03-03 10:31:40 CET --- Update released for openSUSE 13.1. Resolved fixed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.