Inconsistent metadata on VM's VG'ss

nardusg · Post by **nardusg** » 2019/08/13 09:45:14

Hi There

Hope you are all well. We got this weird issue at the moment. Let me explain.

We are on ovirt 4.3.5. We use Centos 7.6 and when we do an update on the VM's the VM's can not boot into multi user mode. It complains that the root mount can't be found. When you boot using ISO and rescue mode you can see the disks. When you chroot into the VM and run pvscan twice your VM can be rebooted and it is fixed. We don't know if this is Centos based or maybe something on ovirt. Screenshots below. Any help would be appreciated.

Should I log a bug request ?

Thanks

Nardus

Post by **TrevorH** » 2019/08/13 09:50:38

So what is updated when you "do an update"? I presume the kernel must be involved? Does it create the initramfs file for it in /boot correctly? Does it create the entry in /boot/grub2/grub.cfg correctly? I'd suggest scrolling back through the console messages to find out the actual source of the problem.

nardusg · Post by **nardusg** » 2019/08/13 09:52:48

Yes, all goes fine, no errors that is visible. On reboot it just take long and then dracut times out.

nardusg · Post by **nardusg** » 2019/08/14 11:43:04

Hi

So this seems to be related to lvmetad and the last upgrade that is in the above screenshot. If disable lvmetad in /etc/lvm/lvm.conf and systemctl, I then run pvscan and rebuild using dracut. My VM's don't display inconsistent metadata anymore. Also appear to happen only to more than one disk. Still investigating.

So solutions is for someone that get the same type of issue. Will open a bug if there is more people with the same issue.

Ciao

Nar

tony_down_under · Post by **tony_down_under** » 2019/08/14 13:09:37

Are the VMs clones? What is your storage?

tony_down_under · Post by **tony_down_under** » 2019/08/15 06:25:10

I post my questions because I think you are hitting issues due to this https://blogs.ovirt.org/2017/12/lvm-con ... -easy-way/

The host scans and mounts the volumes of the guest within itself by default. This has caused me corruption and outages, because it is/was not included in the documentation. So I had to find out the hard way.

The fix back then was to configure LVM filter manually with Red Hats help. There is now a CLI that will discover and configure the filter for you. I suggest to use that because after they introduced the tool, my first host that went down for yum update did not boot due to the filter but was fine up until that point which was one or two years.

nardusg · Post by **nardusg** » 2019/08/15 08:03:52

Thanks, will check it out

CentOS

Inconsistent metadata on VM's VG'ss

Inconsistent metadata on VM's VG'ss

Re: Inconsistent metadata on VM's VG'ss

Re: Inconsistent metadata on VM's VG'ss

Re: Inconsistent metadata on VM's VG'ss

Re: Inconsistent metadata on VM's VG'ss

Re: Inconsistent metadata on VM's VG'ss

Re: Inconsistent metadata on VM's VG'ss