Hi,

I just wanted to update that NFS is working= n=3D ow with ovirt-node-iso-2.5.5-0.1.fc17,
but I had to change /etc/nfsmount= =3D .conf in the following line:

89 # Enable File Locking

<=3D span lang=3D3DEN-US style=3D3D'font-family:"Courier New";color:#1F497D'>90 = # Lo=3D ck=3D3DTrue (seems to be true per default, although commented out)=3D

=3D
to:

# Enable = File=3D Locking

Lock=3D3DFalse=3D

Is there anybody else, who is runni= ng i=3D n the same problem?

Thanks in advance!<= /o:p=3D >

Kind regards, Sven.

&nbs=3D p;

<=3D span style=3D3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fare= as=3D t-language:DE'>Von: Sven Knohsalla
Gesend= =3D et: Donnerstag, 8. November 2012 15:55
An: users(a)ovirt.org<= br=3D >Betreff: NFS issue using ovirt-node-iso-2.5.5-0.1.fc17

Hi,

just created a test environment, incl= udin=3D g ovirt-engine 3.1 + ovirt-node-iso-2.5.5-0.1.fc17 + qnap iscsi + qnap nas = =3D (NFSv3).

i= SCSI=3D connection is working fine.
When connecting to Export/ISO Domain via we= =3D bgui the progress is taking forever (waited ~ 10 mins)

Back to console I first tried to conn= ect =3D from ovirt-engine to nfs storage of our NAS:

showmount -e 172.16.101.95 ->Exp=3D ort list for 172.16.101.95:

/NFS-ISO01

/Export-NFS01

/…

<= p =3D class=3D3DMsoNormal>mount -t nfs 172.16.101.95:/Export= -NFS=3D 01 /mnt/nastest/

mount ->

172.16.101.95:/Export-NFS01/ on /mnt/nastest type nfs (rw,relatime,vers=3D= 3D=3D 3,rsize=3D3D32768,wsize=3D3D32768,namlen=3D3D255,hard,proto=3D3Dtcp,timeo= =3D3D600,ret=3D rans=3D3D2,sec=3D3Dsys,
mountaddr=3D3D172.16.101.95,mountvers=3D3D3,moun= tport=3D3D=3D 56272,mountproto=3D3Dudp,local_lock=3D3Dnone,addr=3D3D172.16.101.95)

Touching a file on= mou=3D ntpoint is working,too.

On ovirt-node:

showmount -e 172.16.101.95->
Export list for 172.16.101.95:

/NFS-ISO01<= o:p>=3D

/Export-NFS01<= o:p>=3D

/…
mo=3D unt -t nfs 172.16.101.95:/Export-NFS01 /mnt/nastest/ ->
mount.nfs: rp= =3D c.statd is not running but is required for remote locking.

mount.nfs: Either use '-o = nolo=3D ck' to keep locks local, or start statd.

mount.nfs: an incorrect mount option was speci= fi=3D ed

mount -t nfs 172.16.101.95:/Export-NFS01 /mnt/nastest/ -o nolock = =3D ->
working (also for vdsm)!

There’s no firewall between = =3D NAS and node (except node fw)

<= sp=3D an lang=3D3DEN-US>
rpcbind isn’t installed on node:
http://gerrit.ovirt.org/#/c/4720/= =3D

It seems t= he p=3D ackage isn’t needed anymore by this post in gerrit?= =3D

Well, how to proceed here?
Am I= get=3D ting my wires crossed here or just missed a configuration?

Thx in advance!=

=3D

Best,

Sven.

Sven Knohsall= a | Sy=3D stem Administration

=3D

Office +49 631 68036 433 | Fax +49 631 680= =3D 36 111 |E-Mail s.knohsalla(a)netbiscuits.com | S= ky=3D pe: netbiscuits.admin

<= =3D p class=3D3DMsoNormal>Netbiscuits GmbH | Europaallee 10 | 67657 | GERMANY