Hi Johan,

Can you please share the vdsm and engine logs.

Also, it won't harm to also get the sanlock logs just in case sanlock
was configured to save all debugging in a log file (see
Try to share the sanlock ouput by running  'sanlock client status',
'sanlock client log_dump'.


On Thu, Jul 27, 2017 at 6:18 PM, Johan Bernhardsson <jo...@kafit.se> wrote:
> Hello,
> The ids file for sanlock is broken on one setup. The first host id in
> the file is wrong.
> From the logfile i have:
> verify_leader 1 wrong space name 0924ff77-ef51-435b-b90d-50bfbf2e�ke7
> 0924ff77-ef51-435b-b90d-50bfbf2e8de7 /rhev/data-center/mnt/glusterSD/
> Note the broken char in the space name.
> This also apears. And it seams as the hostid too is broken in the ids
> file:
> leader4 sn 0924ff77-ef51-435b-b90d-50bfbf2e�ke7 rn ��7 afa5-3a91-415b-
> a04c-221d3e060163.vbgkvm01.a ts 4351980 cs eefa4dd7
> Note the broken chars there as well.
> If i check the ids file with less or strings the first row where my
> vbgkvm01 host are. That has broken chars.
> Can this be repaired in some way without taking down all the virtual
> machines on that storage?
> /Johan
> _______________________________________________
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
Users mailing list

Reply via email to