Comment # 11 on bug 901859 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