<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Mar 1, 2016 at 5:07 PM, <a href="mailto:paf1@email.cz">paf1@email.cz</a> <span dir="ltr"><<a href="mailto:paf1@email.cz" target="_blank">paf1@email.cz</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div text="#000066" bgcolor="#FFFFFF">
Hello, can anybody explain this error no.13 ( open file ) in
sanlock.log .<br></div></blockquote><div><br></div><div>This is EACCES</div><div><br></div><div>Can you share the outoput of:</div><div><br></div><div> ls -lh /rhev/data-center/mnt/<server>:<_path>/<sd_uuid>/dom_md</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div text="#000066" bgcolor="#FFFFFF">
<br>
The size of "ids" file is zero (0)<br></div></blockquote><div><br></div><div>This is how we create the ids file when initializing it.</div><div><br></div><div>But then we use sanlock to initialize the ids file, and it should be 1MiB after that.</div><div><br></div><div>Is this ids files created by vdsm, or one you created yourself?</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div text="#000066" bgcolor="#FFFFFF">
2016-02-28 03:25:46+0100 269626 [1951]: open error -13
/rhev/data-center/mnt/glusterSD/localhost:_1KVM12-P4/7f52b697-c199-4f58-89aa-102d44327124/dom_md/ids<br>
2016-02-28 03:25:46+0100 269626 [1951]: s187985 open_disk
/rhev/data-center/mnt/glusterSD/localhost:_1KVM12-P4/7f52b697-c199-4f58-89aa-102d44327124/dom_md/ids
error -13<br>
2016-02-28 03:25:56+0100 269636 [11304]: s187992 lockspace
7f52b697-c199-4f58-89aa-102d44327124:1:/rhev/data-center/mnt/glusterSD/localhost:_1KVM12-P4/7f52b697-c199-4f58-89aa-102d44327124/dom_md/ids:0<br>
<br>
If the main problem is about zero file size, can I regenerate this
file online securely , with no VM dependence ????<br></div></blockquote><div><br></div><div>Yes, I think I already referred to the instructions how to do that in a previous mail.<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div text="#000066" bgcolor="#FFFFFF">
<br>
<br>
dist = RHEL - 7 - 2.1511<br>
kernel = 3.10.0 - 327.10.1.el7.x86_64<br>
KVM = 2.3.0 - 29.1.el7<br>
libvirt = libvirt-1.2.17-13.el7_2.3<br>
vdsm = vdsm-4.16.30-0.el7<br>
GlusterFS = glusterfs-3.7.8-1.el7<br>
<br>
<br>
regs.<br>
Pavel<br>
</div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">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>
<br></blockquote></div><br></div></div>