В Tue, 04 Feb 2014 13:30:05 -0500
Robert Schweikert
On 02/04/2014 12:58 PM, Andrey Borzenkov wrote:
В Tue, 04 Feb 2014 11:51:16 -0500 Robert Schweikert
пишет: The solution was to set
use_lvmetad = 0
in /etc/lvm/lvm.conf
Actually, intended solution is "systemctl enable lvm2-lvmetad.socket" but whatever works :)
Tried that and still ended up with a non operational setup. Turning the new fancy feature off worked.
Are you using LVM for root?
No. All my volumes are for other directory trees, /home, /srv, and other stuff. Pretty much the same situation as in the bug.
In the bug it was also mentioned that enabling lvmetad did not work. It may possibly be an order thing. But even after reading the related fedora bug I was not certain abut what the order should be to get things to work as intended with
use_lvmetad = 1
You do not need to enable lvm2-lvmetad.service. You need to enable lvm2-lvmetad.*socket*. This way service is auto-started as soon as lvm tries to connect to socket. Having service alone enabled would of course imply race condition against udev. Enabling socket works for me for non-system group.
It does not look like mkinitrd installs lvmetad (or respective udev rule) in initrd, but it does copy /etc/lvm.conf. I wonder what lvm does in this case; probably waits for lvmetad ...
That would be a problem
Actually not, if lvmetad is not available, it falls back to old behavior. So you get nagging warnings but that's all. The problem with non-system group is that with lvmetad set in lvm.conf but disabled nothing activates those groups. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org