-------- Eredeti levél --------
Feladó: Strahil Nikolov < [email protected] (Link ->
mailto:[email protected]) >
Dátum: 2020 április 26 07:57:43
Tárgy: Re: [ovirt-users] Ovirt vs lvm?
Címzett: [email protected] (Link -> mailto:[email protected])
On April 25, 2020 11:07:23 PM GMT+03:00, [email protected] 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?
>_______________________________________________
>Users mailing list -- [email protected]
>To unsubscribe send an email to [email protected]
>Privacy Statement: https://www.ovirt.org/privacy-policy.html
>oVirt Code of Conduct:
>https://www.ovirt.org/community/about/community-guidelines/
>List Archives:
>https://lists.ovirt.org/archives/list/[email protected]/message/AHKCLRZUWO4UVCFRBXN6GETS4M46A2FQ/
I haven't seen such issue so far, but I can only recommend yoiu to clone such
VM next time, so you can try to figure out what is going on.
During the repair, have you tried rebuilding the initramfs after the issue
happens ?
Best Regards,
Strahil Nikolov
Thanks for advice!
Definitely yes, i make a new initramfs by dracut.
When this error occure, the locking_type parameter in darcut lvm.conf file
changed to 4.
I write back to 1: lvm vhchange -ay --config ' global {locking_type=1} '
then write back the locking_type in /etc/lvm/lvm.conf to 1.
Then exit and (if i have a lucky day) the dracut -v -f build's a new initramfs
and the vm works fine.
The issue appear's in couple, so if i found a vm for this "error" one in the
others running vms has this error too.
csabany_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/[email protected]/message/JPJLMNBHBZLBQ7DYCHV7DB53QTE3XBOO/
