https://bugzilla.novell.com/show_bug.cgi?id=871704
https://bugzilla.novell.com/show_bug.cgi?id=871704#c57
--- Comment #57 from Andrey Borzenkov 2014-04-19 05:35:49 UTC ---
I can reproduce it now (not with exact symptoms) in QEMU VM: openSUSE 32 bit,
minimal install on a single physical disk (non LVM!), all current patches,
added three more drives after initial installation and created PV on them.
During reboot I get:
Apr 19 09:27:24 linux-qqqf LVM: Logical Volume autoactivation enabled.
Apr 19 09:27:24 linux-qqqf LVM: Activation generator successfully completed.
Apr 19 09:27:24 linux-qqqf systemd[1]: Starting LVM2 metadata daemon socket.
Apr 19 09:27:24 linux-qqqf systemd[1]: Listening on LVM2 metadata daemon
socket.
Apr 19 09:27:29 linux-qqqf systemd[1]: Starting LVM2 metadata daemon...
Apr 19 09:27:29 linux-qqqf systemd[1]: Started LVM2 metadata daemon.
Apr 19 09:27:29 linux-qqqf systemd-udevd[247]: '/sbin/lvm pvscan --cache
--activate ay --major 8 --minor 33' [870] terminated by signal 6 (Aborted)
Apr 19 09:27:29 linux-qqqf systemd-udevd[249]: '/sbin/lvm pvscan --cache
--activate ay --major 8 --minor 17' [874] terminated by signal 6 (Aborted)
Apr 19 09:27:29 linux-qqqf systemd-udevd[248]: '/sbin/lvm pvscan --cache
--activate ay --major 8 --minor 49' [871] terminated by signal 6 (Aborted)
And no device is present. Running "pvs" after reboot apparently triggers rescan
from lvmetad and devices appear.
So yes, there it definitely an issue with multiple PVs. This may be hidden if
root itself is on LVM so initrd does initial scan and configures them; but pure
lvmetad fails far too easily.
--
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.