<p dir="ltr">Updating from sanlock-2.6-4.fc18 to sanlock-2.6-7.fc18 fixed it. Huge thanks!</p>
<div class="gmail_quote">On Mar 20, 2013 10:24 PM, "Federico Simoncelli" <<a href="mailto:fsimonce@redhat.com">fsimonce@redhat.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
----- Original Message -----<br>
> From: "Limor Gavish" <<a href="mailto:lgavish@gmail.com">lgavish@gmail.com</a>><br>
> To: "Federico Simoncelli" <<a href="mailto:fsimonce@redhat.com">fsimonce@redhat.com</a>><br>
> Cc: "Yuval M" <<a href="mailto:yuvalme@gmail.com">yuvalme@gmail.com</a>>, <a href="mailto:users@ovirt.org">users@ovirt.org</a>, "Nezer Zaidenberg" <<a href="mailto:nzaidenberg@mac.com">nzaidenberg@mac.com</a>>, "Eli Mesika"<br>
> <<a href="mailto:emesika@redhat.com">emesika@redhat.com</a>>, "Maor Lipchuk" <<a href="mailto:mlipchuk@redhat.com">mlipchuk@redhat.com</a>><br>
> Sent: Wednesday, March 20, <a href="tel:2013" value="+9722013">2013</a> 9:02:35 PM<br>
> Subject: Re: [Users] Failing to attach NFS data storage domain (Ovirt 3.2)<br>
><br>
> Thank you very much for your response.<br>
><br>
><br>
> Attached VDSM logs as you requested (The VDSM logs where the NFS<br>
> domain was created were missing so we had to recreate the NFS<br>
> domain, therefore the sdUUID has changed).<br>
> Here is the rest of the commands you asked:<br>
><br>
><br>
> [root@bufferoverflow wil]# mount -t nfs<br>
> bufferoverflow:/home/BO_Ovirt_Storage /mnt/tmp<br>
> [root@bufferoverflow wil]# cd<br>
> /mnt/tmp/1083422e-a5db-41b6-b667-b9ef1ef244f0/dom_md/<br>
> [root@bufferoverflow dom_md]# ls -l<br>
> total <a href="tel:2052" value="+9722052">2052</a><br>
> -rw-rw---- 1 vdsm kvm 1048576 Mar <a href="tel:20%2021" value="+9722021">20 21</a>:46 ids<br>
> -rw-rw---- 1 vdsm kvm 0 Mar <a href="tel:20%2021" value="+9722021">20 21</a>:45 inbox<br>
> -rw-rw---- 1 vdsm kvm 2097152 Mar <a href="tel:20%2021" value="+9722021">20 21</a>:45 leases<br>
> -rw-r--r-- 1 vdsm kvm 311 Mar 20 21:45 metadata<br>
> -rw-rw---- 1 vdsm kvm 0 Mar 20 21:45 outbox<br>
> [root@bufferoverflow dom_md]# sanlock direct dump ids<br>
<br>
Sorry I should have mentioned that if you use root_squash for your nfs<br>
share you have to switch to the vdsm user:<br>
<br>
(root)# su -s /bin/sh vdsm<br>
(vdsm)$ cd /mnt/tmp/<sduuid>/dom_md/<br>
<br>
(vdsm)$ sanlock direct dump ids<br>
(and now you should be able to see the output)<br>
<br>
If the output is still empty then used hexdump -C to inspect it<br>
(and eventually post it here compressed).<br>
<br>
Another important thing that you should check is:<br>
<br>
# ps fax | grep sanlock<br>
<br>
If the output doesn't look like the following:<br>
<br>
1966 ? SLs 0:00 wdmd -G sanlock<br>
<a href="tel:2036" value="+9722036">2036</a> ? SLsl 0:00 sanlock daemon -U sanlock -G sanlock<br>
<a href="tel:2037" value="+9722037">2037</a> ? S 0:00 \_ sanlock daemon -U sanlock -G sanlock<br>
<br>
Then I suggest you to update sanlock to the latest build:<br>
<br>
<a href="http://koji.fedoraproject.org/koji/buildinfo?buildID=377815" target="_blank">http://koji.fedoraproject.org/koji/buildinfo?buildID=377815</a><br>
(sanlock-2.6-7.fc18)<br>
<br>
And eventually if after rebooting the problem persists, please post<br>
also the sanlock log (/var/log/sanlock.log)<br>
<br>
> Please note, the VDSM is running as a system service (it was<br>
> installed from a package) while ovirt-engine was built from sources<br>
> and thus is not running as root. Is this an issue?<br>
<br>
It shouldn't be.<br>
<br>
--<br>
Federico<br>
</blockquote></div>