-------- Eredeti lev&#233;l --------<br />
Felad&#243;: Strahil Nikolov &#60; hunter86_bg@yahoo.com (Link -&#62; mailto:hunter86_bg@yahoo.com) &#62;<br />
D&#225;tum: 2020 &#225;prilis 26 07:57:43<br />
T&#225;rgy: Re: [ovirt-users] Ovirt vs lvm?<br />
C&#237;mzett: csabany@freemail.hu (Link -&#62; mailto:csabany@freemail.hu)<br />
On April 25, 2020 11:07:23 PM GMT+03:00, csabany@freemail.hu wrote:<br />
&#62;Hi,<br />
&#62;<br />
&#62;Our production ovirt system looks like: standalone management server,<br />
&#62;vesion 4.3.9, 6 clusters, 28 nodes (v4.2, v4.3) , one storage domain,<br />
&#62;(FC SAN Storages), centos7 vm-s , and some windows vms.<br />
&#62;I have a returning problem. Sometime when i power off a vm and power on<br />
&#62;again , i get an error message our linux vm (when we use lvm of<br />
&#62;course): dracut: Read-only locking type set. Write locks are<br />
&#62;prohibited., dracut: Can&#39;t get lock for vg.<br />
&#62;I can repair only 70% of damaged vm.<br />
&#62;I tried to localize the problem, but a can`t. The error occured<br />
&#62;randomly every cluster, every storage on last 2 years.<br />
&#62;Has anyone ever encountered such a problem?<br />
&#62;_______________________________________________<br />
&#62;Users mailing list -- users@ovirt.org<br />
&#62;To unsubscribe send an email to users-leave@ovirt.org<br />
&#62;Privacy Statement: https://www.ovirt.org/privacy-policy.html<br />
&#62;oVirt Code of Conduct:<br />
&#62;https://www.ovirt.org/community/about/community-guidelines/<br />
&#62;List Archives:<br />
&#62;https://lists.ovirt.org/archives/list/users@ovirt.org/message/AHKCLRZUWO4UVCFRBXN6GETS4M46A2FQ/<br />
I haven&#39;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.<br />
During the repair, have you tried rebuilding the initramfs after the issue happens ?<br />
Best Regards,<br />
Strahil Nikolov<br />
<br />
Thanks for advice!<br />
<br />
Definitely yes, i make a new initramfs by dracut.<br />
When this error occure, the locking_type parameter in darcut lvm.conf file changed to 4.<br />
I write back to 1: lvm vhchange -ay --config &#39; global {locking_type=1} &#39;<br />
then write back the locking_type in /etc/lvm/lvm.conf to 1.<br />
Then exit and (if i have a lucky day) the dracut -v -f build&#39;s a new initramfs and the vm works fine.<br />
<br />
The issue appear&#39;s in couple, so if i found a vm for this &#34;error&#34; one in the others running vms has this error too.<br />
<br />
csabany