<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Sun, Jul 30, 2017 at 4:24 PM Maor Lipchuk <<a href="mailto:mlipchuk@redhat.com">mlipchuk@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sun, Jul 30, 2017 at 4:24 PM, Maor Lipchuk <<a href="mailto:mlipchuk@redhat.com" target="_blank">mlipchuk@redhat.com</a>> wrote:<br>
> Hi David,<br>
Sorry, I meant Johan<br>
<br>
><br>
> I'm not sure how it got to that character in the first place.<br>
> Nir, Is there a safe way to fix that while there are running VMs?<br></blockquote><div><br></div><div>Reparing sanlock ids file is explained here:</div><div><a href="http://lists.ovirt.org/pipermail/users/2016-February/038051.html">http://lists.ovirt.org/pipermail/users/2016-February/038051.html</a><br></div><div><br></div><div>If you cannot put the domain into maintenance, you can try to repair</div><div>the ids file while the domain is online. This may work for you, but</div><div>we don't support this.</div><div><br></div><div>Nir</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
><br>
> Regards,<br>
> Maor<br>
><br>
> On Sun, Jul 30, 2017 at 11:58 AM, Johan Bernhardsson <<a href="mailto:johan@kafit.se" target="_blank">johan@kafit.se</a>> wrote:<br>
>> (First reply did not get to the list)<br>
>><br>
>> From sanlock.log:<br>
>><br>
>> 2017-07-30 10:49:31+0200 1766275 [1171]: s310751 lockspace 0924ff77-<br>
>> ef51-435b-b90d-50bfbf2e8de7:1:/rhev/data-<br>
>> center/mnt/glusterSD/vbgsan02:_fs02/0924ff77-ef51-435b-b90d-<br>
>> 50bfbf2e8de7/dom_md/ids:0<br>
>> 2017-07-30 10:49:31+0200 1766275 [10496]: verify_leader 1 wrong space<br>
>> name 0924ff77-ef51-435b-b90d-50bfbf2e<D5>ke7 0924ff77-ef51-435b-b90d-<br>
>> 50bfbf2e8de7 /rhev/data-center/mnt/glusterSD/vbgsan02:_fs02/0924ff77-<br>
>> ef51-435b-b90d-50bfbf2e8de7/dom_md/ids<br>
>> 2017-07-30 10:49:31+0200 1766275 [10496]: leader1 delta_acquire_begin<br>
>> error -226 lockspace 0924ff77-ef51-435b-b90d-50bfbf2e8de7 host_id 1<br>
>> 2017-07-30 10:49:31+0200 1766275 [10496]: leader2 path /rhev/data-<br>
>> center/mnt/glusterSD/vbgsan02:_fs02/0924ff77-ef51-435b-b90d-<br>
>> 50bfbf2e8de7/dom_md/ids offset 0<br>
>> 2017-07-30 10:49:31+0200 1766275 [10496]: leader3 m 12212010 v 30003 ss<br>
>> 512 nh 0 mh 4076 oi 1 og 2031079063 lv 0<br>
>> 2017-07-30 10:49:31+0200 1766275 [10496]: leader4 sn 0924ff77-ef51-<br>
>> 435b-b90d-50bfbf2e<D5>ke7 rn <93><F6>7^\afa5-3a91-415b-a04c-<br>
>> 221d3e060163.vbgkvm01.a ts 4351980 cs eefa4dd7<br>
>> 2017-07-30 10:49:32+0200 1766276 [1171]: s310751 add_lockspace fail<br>
>> result -226<br>
>><br>
>><br>
>> vdsm logs doesnt have any errors and engine.log does not have any<br>
>> errors.<br>
>><br>
>> And if i check the ids file manually. I can see that everything in it<br>
>> is correct except for the first host in the cluster where the space<br>
>> name and host id is broken.<br>
>><br>
>><br>
>> /Johan<br>
>><br>
>> On Sun, 2017-07-30 at 11:18 +0300, Maor Lipchuk wrote:<br>
>>> Hi Johan,<br>
>>><br>
>>> Can you please share the vdsm and engine logs.<br>
>>><br>
>>> Also, it won't harm to also get the sanlock logs just in case sanlock<br>
>>> was configured to save all debugging in a log file (see<br>
>>> <a href="http://people.redhat.com/teigland/sanlock-messages.txt)" rel="noreferrer" target="_blank">http://people.redhat.com/teigland/sanlock-messages.txt)</a>).<br>
>>> Try to share the sanlock ouput by running 'sanlock client status',<br>
>>> 'sanlock client log_dump'.<br>
>>><br>
>>> Regards,<br>
>>> Maor<br>
>>><br>
>>> On Thu, Jul 27, 2017 at 6:18 PM, Johan Bernhardsson <<a href="mailto:johan@kafit.se" target="_blank">johan@kafit.se</a>><br>
>>> wrote:<br>
>>> ><br>
>>> > Hello,<br>
>>> ><br>
>>> > The ids file for sanlock is broken on one setup. The first host id<br>
>>> > in<br>
>>> > the file is wrong.<br>
>>> ><br>
>>> > From the logfile i have:<br>
>>> ><br>
>>> > verify_leader 1 wrong space name 0924ff77-ef51-435b-b90d-<br>
>>> > 50bfbf2e�ke7<br>
>>> > 0924ff77-ef51-435b-b90d-50bfbf2e8de7 /rhev/data-<br>
>>> > center/mnt/glusterSD/<br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> > Note the broken char in the space name.<br>
>>> ><br>
>>> > This also apears. And it seams as the hostid too is broken in the<br>
>>> > ids<br>
>>> > file:<br>
>>> ><br>
>>> > leader4 sn 0924ff77-ef51-435b-b90d-50bfbf2e�ke7 rn ��7 afa5-3a91-<br>
>>> > 415b-<br>
>>> > a04c-221d3e060163.vbgkvm01.a ts 4351980 cs eefa4dd7<br>
>>> ><br>
>>> > Note the broken chars there as well.<br>
>>> ><br>
>>> > If i check the ids file with less or strings the first row where my<br>
>>> > vbgkvm01 host are. That has broken chars.<br>
>>> ><br>
>>> > Can this be repaired in some way without taking down all the<br>
>>> > virtual<br>
>>> > machines on that storage?<br>
>>> ><br>
>>> ><br>
>>> > /Johan<br>
>>> > _______________________________________________<br>
>>> > Users mailing list<br>
>>> > <a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
>>> > <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
</blockquote></div></div>