http://bugzilla.suse.com/show_bug.cgi?id=898913
--- Comment #7 from Werner Flamme
(In reply to Werner Flamme from comment #5)
The lvm2-lvmetad is a metadata cache daemon. You can also use traditional way to deal with metadata. The warning messages are noisy but actually harmless. That is because you disabled lvmetad(use_lvmetad=0) but the lvmetad daemon is running. In this occasion lvmetad will not be used. Why the daemon is running, it is because lvm2 package updating will 'try-restart lvm2-lvmetad.socket', which will start lvm2-lvmetad.service, which is a feature of systemd. There are two ways to avoid the warning messages: 1. stop .service manually. 2. enable lvmetad by set use_lvmetad=1 in /etc/lvm/lvm.conf
This did the trick! Stopping the service, editing the parameter and restarting the service brought the LVM groups to visibility :)
The warning texts are gone, but the volume groups on an external disk (USB3) are still not recognized. In fact, I often need the partprobe command to have the system recognize the disk (typically /dev/sdb) at all. And I do not know what to do about the lvmetad warning. You mean if you not excute partprobe, lv cannot be activated?
Yes, before I changed the parameter, fdisk sometimes ignored the disk completely, or the non-LVM partitions were recognized, but not the volumes (the volume group) in the LVM partition. Since I set use_lvmetad=1, the old behaviour is back, and all volumes are displayed right after the USB disk is connected. Thank you! Regards, Werner -- You are receiving this mail because: You are on the CC list for the bug.