Re: [Users] Failing to attach NFS data storage domain (Ovirt 3.2)

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