Sure. vdsm-tool should be disabling lvmetad on the host automatically.
Maybe some of the hosts were fresh installed and others have been upgraded
from older versions? In any case, you should be able to run on any host in
maintenance mode:
sudo vdsm-tool configure --force
And this should edit the lvm.conf file to disable lvmetad globally and also
prevent the lvmetad service from starting.
On Wed, Oct 4, 2017 at 10:02 AM, Nicolas Ecarnot <nicolas(a)ecarnot.net>
wrote:
Le 04/10/2017 à 15:30, Adam Litke a écrit :
>
> On Wed, Oct 4, 2017 at 4:12 AM Nicolas Ecarnot <nicolas(a)ecarnot.net
> <mailto:nicolas@ecarnot.net>> wrote:
>
> Adam,
>
> TL;DR : You nailed it!
>
>
> Great! Glad you're back up and running. One additional note about LVM
> commands. It's dangerous to use lvmetad for some commands while vdsm is
> running since it will not use lvmetad. You could end up with conflicting
> operations. In general it's safest to not issue any lvm commands while the
> host is activated but if you must, don't forget to disable lvmetad for all
> commands.
>
OK.
Is it worth trying to understand why amongst our 32 hosts in 2 DC, all in
the same version (OS, vdsm, qemu packages...) some are showing they're
using lvmetad and some not?
--
Nicolas ECARNOT
--
Adam Litke