http://bugzilla.opensuse.org/show_bug.cgi?id=901859 Olav Reinert changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|LVM2: lvs command gives |LVM2: lvs command gives |error message about lvmetad |warning message about | |lvmetad -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=901859 Maciej Pilichowski changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bluedzins@wp.pl -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=901859 --- Comment #2 from Liuhua Wang --- When lvmetad daemon initiates, it will check lvm.conf whether user_lvmeated =1 is set, if user_lvmetad = 0 but you are running lvmeatd, there will be the warning. void lvmetad_init(struct cmd_context *cmd) { if (!_lvmetad_use && !access(LVMETAD_PIDFILE, F_OK)) log_warn("WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!"); ..... I think if you don't want to see the warning, please set user_lvmetad = 0. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=901859 --- Comment #4 from Liuhua Wang --- (In reply to Björn Voigt from comment #3)

Where can I find user_lvmetad? (No hits in /etc/lvm and "man lvm.conf")

I am really sorry, I made a spelling miss. should be "use_lvmetad". -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=901859 --- Comment #5 from Liuhua Wang --- Can we close this bug as invalid? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=901859 --- Comment #7 from Martin Pluskal --- On current openSUSE-Factory: # systemctl status lvm2-lvmetad.service lvm2-lvmetad.service - LVM2 metadata daemon Loaded: loaded (/usr/lib/systemd/system/lvm2-lvmetad.service; enabled) Active: active (running) since Sat 2014-11-29 17:35:59 CET; 1 day 15h ago Docs: man:lvmetad(8) Main PID: 577 (lvmetad) CGroup: /system.slice/lvm2-lvmetad.service └─577 /sbin/lvmetad -f # grep use_lvmetad /etc/lvm/lvm.conf # If lvmetad has been running while use_lvmetad was 0, it MUST be stopped # before changing use_lvmetad to 1 and started again afterwards. # If use_lvmetad set to 1, please make sure lvm2-lvmetad.socket is started use_lvmetad = 0 Which is obviously not correct. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=901859 Bruno Friedmann changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bruno@ioda-net.ch --- Comment #9 from Bruno Friedmann --- This is also true on 13.1 and certainly would be a nice maintenance update -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=901859 Kenneth Ingham changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ingham@i-pi.com --- Comment #11 from Kenneth Ingham --- This problem still exists in aq fresh 13.2 which was then upgraded to Tumbleweed: # systemctl status lvm2-lvmetad.service lvm2-lvmetad.service - LVM2 metadata daemon Loaded: loaded (/usr/lib/systemd/system/lvm2-lvmetad.service; enabled) Active: active (running) since Thu 2014-12-18 13:05:28 MST; 1min 7s ago Docs: man:lvmetad(8) Main PID: 23575 (lvmetad) CGroup: /system.slice/lvm2-lvmetad.service └─23575 /sbin/lvmetad -f # grep use_lvmetad /etc/lvm/lvm.conf # If lvmetad has been running while use_lvmetad was 0, it MUST be stopped # before changing use_lvmetad to 1 and started again afterwards. # If use_lvmetad set to 1, please make sure lvm2-lvmetad.socket is started use_lvmetad = 0 # lvs WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it! connect() failed on local socket: No such file or directory Internal cluster locking initialisation failed. WARNING: Falling back to local file-based locking. Volume Groups with the clustered attribute will be inaccessible. LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert KaliLinux Internal -wi-a----- 20.00g OS Internal -wi-ao---- 80.00g home Internal -wi-ao---- 1.71t swap Internal -wi-ao---- 16.00g -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=901859 --- Comment #13 from Kenneth Ingham --- # grep lvm /usr/lib/systemd/system-preset/90-default-openSUSE.preset enable lvm2-lvmetad.socket -- You are receiving this mail because: You are on the CC list for the bug.

(In reply to Kenneth Ingham from comment #13)

...

# grep lvm /usr/lib/systemd/system-preset/90-default-openSUSE.preset enable lvm2-lvmetad.socket Thank you for your confirm test and information provide.

I think it is because only delete `enable lvm2-lvmetad.service` from system-preset/90-default-openSUSE.preset is not enough for disabling lvm2-lvmetad.service. We also need to delete lvm2-lvmetad.service from %service_add_pre/post, %service_del_preun/postun in lvm2.spec. No, those do not enable them, they just take care of their registrations, and

http://bugzilla.opensuse.org/show_bug.cgi?id=901859 --- Comment #15 from Martin Pluskal --- (In reply to Liuhua Wang from comment #14) they are supposed to be there - see https://en.opensuse.org/openSUSE:Systemd_packaging_guidelines#Register_servi... and /etc/rpm/macros.systemd . Please revert this change.

I already submitted request to opensuse.

Also I am not sure why "enable lvm2-lvmetad.socket" is in presets, but I guess that correct solution would be to remove it. -- You are receiving this mail because: You are on the CC list for the bug.