Achim Gratz writes:
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
Supposedly fixed with the new Tumbleweed version. I'll keep an eye on it since it was still running after the first reboot and showing as enabled (I have disabled it manually now). Something is still wrong with the socket configuration: --8<---------------cut here---------------start------------->8--- # systemctl status lvm2-lvmetad.socket lvm2-lvmetad.socket - LVM2 metadata daemon socket Loaded: loaded (/usr/lib/systemd/system/lvm2-lvmetad.socket; enabled) Active: active (running) since Sun 2014-12-07 18:10:53 CET; 51min ago Docs: man:lvmetad(8) Listen: /run/lvm/lvmetad.socket (Stream) Dec 07 18:10:53 Gertrud systemd[1]: [/usr/lib/systemd/system/lvm2-lvmetad.socket:9] Unknown lvalue 'RemoveOnStop' in section 'Socket' --8<---------------cut here---------------end--------------->8---
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. […]
Something enabled an LVM cluster (uh, what?!?), this messages are gone after an lvmconf --disable-cluster corrects that. I have no idea what could have enabled a cluster in my LVM setup since it only has a single device anyway. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org