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

[root@bufferoverflow dom_md]#

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?

On Wed, Mar 20, 2013 at 8:07 PM, Federico Simoncelli <fsimonce@redhat.com> wrote:

----- Original Message -----
> From: "Limor Gavish" <lgavish@gmail.com>

> To: "Eli Mesika" <emesika@redhat.com>
> Cc: "Yuval M" <yuvalme@gmail.com>, users@ovirt.org, "Nezer Zaidenberg" <nzaidenberg@mac.com>
> Sent: Wednesday, March 20, 2013 11:47:49 AM
> Subject: Re: [Users] Failing to attach NFS data storage domain (Ovirt 3.2)
>
> Thank you very much for your reply.
> I attached the vdsm.log

Hi Limor, can you please inspect the status of the NFS mount?

# mkdir /mnt/tmp
# mount -t nfs <your_nfs_share> /mnt/tmp
# cd /mnt/tmp/1902354b-4c39-4707-ac6c-3637aaf1943b/dom_md

And please report the output of:

# ls -l

# sanlock direct dump ids

Can you also include more vdsm logs? More specifically the ones where the
NFS domain has been created?
(createStorageDomain with sdUUID='1902354b-4c39-4707-ac6c-3637aaf1943b')

Thanks,
--
Federico