Re: [Users] NFS issue using ovirt-node-iso-2.5.5-0.1.fc17

Totally forgot the main problem:**** ** ** This config won’t survive a reboot, so where can I push the button therefore J**** ** ** Best,**** Sven.**** ** ** *Von:* Sven Knohsalla *Gesendet:* Freitag, 9. November 2012 17:35 *An:* users(a)ovirt.org *Betreff:* AW: NFS issue using ovirt-node-iso-2.5.5-0.1.fc17**** ** ** Hi,**** ** ** I just wanted to update that NFS is working now with ovirt-node-iso-2.5.5-0.1.fc17, but I had to change /etc/nfsmount.conf in the following line:**** ** ** 89 # Enable File Locking**** 90 # Lock=True (seems to be true per default, although commented out)**** to:**** ** ** # Enable File Locking**** Lock=False**** ** ** Is there anybody else, who is running in the same problem?**** ** ** Thanks in advance!**** ** ** Kind regards, Sven.**** ** ** ** ** ** ** *Von:* Sven Knohsalla *Gesendet:* Donnerstag, 8. November 2012 15:55 *An:* users(a)ovirt.org *Betreff:* NFS issue using ovirt-node-iso-2.5.5-0.1.fc17**** ** ** Hi,**** ** ** just created a test environment, including ovirt-engine 3.1 + ovirt-node-iso-2.5.5-0.1.fc17 + qnap iscsi + qnap nas (NFSv3).**** iSCSI connection is working fine. When connecting to Export/ISO Domain via webgui the progress is taking forever (waited ~ 10 mins)**** ** ** Back to console I first tried to connect from ovirt-engine to nfs storage of our NAS:**** showmount -e 172.16.101.95 -> Export list for 172.16.101.95:**** /NFS-ISO01**** /Export-NFS01**** /…**** mount -t nfs 172.16.101.95:/Export-NFS01 /mnt/nastest/**** mount ->**** 172.16.101.95:/Export-NFS01/ on /mnt/nastest type nfs (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys, mountaddr=172.16.101.95,mountvers=3,mountport=56272,mountproto=udp,local_lock=none,addr=172.16.101.95) **** Touching a file on mountpoint is working,too.**** ** ** On ovirt-node:**** showmount -e 172.16.101.95-> Export list for 172.16.101.95:**** /NFS-ISO01**** /Export-NFS01**** /… mount -t nfs 172.16.101.95:/Export-NFS01 /mnt/nastest/ -> mount.nfs: rpc.statd is not running but is required for remote locking.*** * mount.nfs: Either use '-o nolock' to keep locks local, or start statd.**** mount.nfs: an incorrect mount option was specified mount -t nfs 172.16.101.95:/Export-NFS01 /mnt/nastest/ -o nolock -> working (also for vdsm)! There’s no firewall between NAS and node (except node fw)**** rpcbind isn’t installed on node: http://gerrit.ovirt.org/#/c/4720/**** It seems the package isn’t needed anymore by this post in gerrit?**** ** ** Well, how to proceed here? Am I getting my wires crossed here or just missed a configuration?**** ** ** Thx in advance!**** ** ** Best,**** Sven.**** ** ** Sven Knohsalla | System Administration**** ** ** Office +49 631 68036 433 | Fax +49 631 68036 111 |E-Mail s.knohsalla(a)netbiscuits.com | Skype: netbiscuits.admin **** Netbiscuits GmbH | Europaallee 10 | 67657 | GERMANY**** _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users Hi,