-------- Eredeti levél --------
Feladó: Gianluca Cecchi < gianluca.cecchi@gmail.com (Link -> mailto:gianluca.cecchi@gmail.com) >
Dátum: 2020 április 26 10:01:27
Tárgy: Re: [ovirt-users] Ovirt vs lvm?
Címzett: csabany@freemail.hu (Link -> mailto:csabany@freemail.hu)
On Sat, Apr 25, 2020 at 10:08 PM < csabany@freemail.hu (Link -> mailto:csabany@freemail.hu) > wrote:
Hi,
Our production ovirt system looks like: standalone management server, vesion 4.3.9, 6 clusters, 28 nodes (v4.2, v4.3) , one storage domain, (FC SAN Storages), centos7 vm-s , and some windows vms.
I have a returning problem. Sometime when i power off a vm and power on again , i get an error message our linux vm (when we use lvm of course): dracut: Read-only locking type set. Write locks are prohibited., dracut: Can't get lock for vg.
I can repair only 70% of damaged vm.
I tried to localize the problem, but a can`t. The error occured randomly every cluster, every storage on last 2 years.
Has anyone ever encountered such a problem?
I think one possible reason could be hypervisor not correctly masking LVM at VM disk level.
There was a bug in the past about this.
Is this a fresh install or arriving from previous versions?
Anyway verify on all your hypervisors what is the output of the command "vgs" and be sure that you only see volume groups related to hypervisors themselves and not inner VMs.
If you have a subset of VMs with the problem, identify if that happens only on particular clusters/hosts, so that you can narrow the analysis to these hypervisors.
HIH,
Gianluca
Thanks the advice.
The hypervisors are "fresh". But the management server arrived from version 3.6 step-by-step (We use this ovirt since 2015).
The issuse occured diffrent clusters, hosts, diffrent HV versions. For example the last but one vm occured on a ibm x3650, ovirt-node v4.2 host and the last on a lenovo, ovirt-node v4.3.
Best
csabany