[Users] add NFS storage domain fails on mount timeout via ovirt
Hi, When trying to add an NFS Export domain via oVirt-engine, it fails on "Problem while trying to mount target". when checking the vdsm.log, it seems that the problem is mount time-out. when I tried to manually run the mount command, in the exact same manner as vdsm, it indeed failed on Connection timed out after ~3 minutes or so: [root@localhost vdsm]# /usr/bin/mount -t nfs -o soft,nosharecache,timeo=600,retrans=6,nfsvers=3 1.2.3.4:/home/ecohen/public/export/engine/storage/195/iscsi-dc/export /rhev/data-center/mnt/11.2.3.4:_home_ecohen_public_export_engine_storage_195_iscsi-dc_export mount.nfs: Connection timed out but - when trying to run the mount command again, with the exact same mount source and mount target, but without any additional parameter, it succeeded (after ~10 seconds): [root@localhost vdsm]# /usr/bin/mount 10.18.57.137:/home/ecohen/public/export/engine/storage/195/iscsi-dc/export /rhev/data-center/mnt/10.18.57.137:_home_ecohen_public_export_engine_storage_195_iscsi-dc_export So I assume that I need to either configure my NFS Export folder differently, or create the storage domain with additional parameters (using the "Advanced Parameters" section in the GUI dialog or similar). any pointers on what exactly should be checked / done? many thanks in advance. ---- Regards, Einav
Einav Cohen wrote:
Hi,
When trying to add an NFS Export domain via oVirt-engine, it fails on "Problem while trying to mount target". when checking the vdsm.log, it seems that the problem is mount time-out.
when I tried to manually run the mount command, in the exact same manner as vdsm, it indeed failed on Connection timed out after ~3 minutes or so:
[root@localhost vdsm]# /usr/bin/mount -t nfs -o soft,nosharecache,timeo=600,retrans=6,nfsvers=3 1.2.3.4:/home/ecohen/public/export/engine/storage/195/iscsi-dc/export /rhev/data-center/mnt/11.2.3.4:_home_ecohen_public_export_engine_storage_195_iscsi-dc_export mount.nfs: Connection timed out
but - when trying to run the mount command again, with the exact same mount source and mount target, but without any additional parameter, it succeeded (after ~10 seconds): [root@localhost vdsm]# /usr/bin/mount 10.18.57.137:/home/ecohen/public/export/engine/storage/195/iscsi-dc/export /rhev/data-center/mnt/10.18.57.137:_home_ecohen_public_export_engine_storage_195_iscsi-dc_export
My guesss its NFSv3 vs NFSv4 Joop
Yes. In my experience when v4 works and v3 does not it's because of firewall issues on the server. -Bob On Dec 11, 2013 11:17 AM, "Joop" <jvdwege@xs4all.nl> wrote:
Einav Cohen wrote:
Hi, When trying to add an NFS Export domain via oVirt-engine, it fails on "Problem while trying to mount target". when checking the vdsm.log, it seems that the problem is mount time-out. when I tried to manually run the mount command, in the exact same manner as vdsm, it indeed failed on Connection timed out after ~3 minutes or so: [root@localhost vdsm]# /usr/bin/mount -t nfs -o soft,nosharecache,timeo=600,retrans=6,nfsvers=3 1.2.3.4: /home/ecohen/public/export/engine/storage/195/iscsi-dc/export /rhev/data-center/mnt/11.2.3.4:_home_ecohen_public_export_ engine_storage_195_iscsi-dc_export mount.nfs: Connection timed out but - when trying to run the mount command again, with the exact same mount source and mount target, but without any additional parameter, it succeeded (after ~10 seconds): [root@localhost vdsm]# /usr/bin/mount 10.18.57.137:/home/ecohen/public/export/engine/storage/195/iscsi-dc/export /rhev/data-center/mnt/10.18.57.137:_home_ecohen_public_ export_engine_storage_195_iscsi-dc_export
My guesss its NFSv3 vs NFSv4
Joop
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Thanks Bob/Joop - checking the "Override Default Options" checkbox and selecting "V4" in the "NFS Version" drop-down within the "Advanced Parameters" section before hitting "OK" in the 'New Domain' dialog did the trick. ---- Regards, Einav ----- Original Message -----
From: "Bob Doolittle" <bob@doolittle.us.com> To: "Joop" <jvdwege@xs4all.nl> Cc: "users" <users@ovirt.org> Sent: Wednesday, December 11, 2013 11:20:01 AM Subject: Re: [Users] add NFS storage domain fails on mount timeout via ovirt
Yes. In my experience when v4 works and v3 does not it's because of firewall issues on the server.
-Bob On Dec 11, 2013 11:17 AM, "Joop" < jvdwege@xs4all.nl > wrote:
Einav Cohen wrote:
Hi, When trying to add an NFS Export domain via oVirt-engine, it fails on "Problem while trying to mount target". when checking the vdsm.log, it seems that the problem is mount time-out. when I tried to manually run the mount command, in the exact same manner as vdsm, it indeed failed on Connection timed out after ~3 minutes or so: [root@localhost vdsm]# /usr/bin/mount -t nfs -o soft,nosharecache,timeo=600, retrans=6,nfsvers=3 1.2.3.4:/home/ecohen/public/ export/engine/storage/195/ iscsi-dc/export /rhev/data-center/mnt/ 11.2.3. 4:_home_ecohen_public_export_ engine_storage_195_iscsi-dc_ export mount.nfs: Connection timed out but - when trying to run the mount command again, with the exact same mount source and mount target, but without any additional parameter, it succeeded (after ~10 seconds): [root@localhost vdsm]# /usr/bin/mount 10.18.57.137:/home/ecohen/ public/export/engine/storage/ 195/iscsi-dc/export /rhev/data-center/mnt/10.18. 57.137:_home_ecohen_public_ export_engine_storage_195_ iscsi-dc_export
My guesss its NFSv3 vs NFSv4
Joop
______________________________ _________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/ mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Be aware that I've also had issues where v4 failed but v3 worked. This happened when trying to export storage from the non-root partition. v4 is fussier in that regard although I'm sure it's configurable somehow. So the most general case I've found is to stick with v3, but make sure the firewall is properly configured on the storage server (or turn it off). In summary, the advantages (I've found) of each: NFSv3: requires no NFS configuration to export storage from non-root partitions (useful if you might want to upgrade your OS some day, although oVirt will have to deliver the feature for importing existing domains simply). NFSv4: requires no firewall configuration (although I thought oVirt handled this automatically - did you change your firewall config after host-deploy?) Good luck, Bob On 12/11/2013 12:02 PM, Einav Cohen wrote:
Thanks Bob/Joop - checking the "Override Default Options" checkbox and selecting "V4" in the "NFS Version" drop-down within the "Advanced Parameters" section before hitting "OK" in the 'New Domain' dialog did the trick.
---- Regards, Einav
----- Original Message -----
From: "Bob Doolittle" <bob@doolittle.us.com> To: "Joop" <jvdwege@xs4all.nl> Cc: "users" <users@ovirt.org> Sent: Wednesday, December 11, 2013 11:20:01 AM Subject: Re: [Users] add NFS storage domain fails on mount timeout via ovirt
Yes. In my experience when v4 works and v3 does not it's because of firewall issues on the server.
-Bob On Dec 11, 2013 11:17 AM, "Joop" < jvdwege@xs4all.nl > wrote:
Einav Cohen wrote:
Hi, When trying to add an NFS Export domain via oVirt-engine, it fails on "Problem while trying to mount target". when checking the vdsm.log, it seems that the problem is mount time-out. when I tried to manually run the mount command, in the exact same manner as vdsm, it indeed failed on Connection timed out after ~3 minutes or so: [root@localhost vdsm]# /usr/bin/mount -t nfs -o soft,nosharecache,timeo=600, retrans=6,nfsvers=3 1.2.3.4:/home/ecohen/public/ export/engine/storage/195/ iscsi-dc/export /rhev/data-center/mnt/ 11.2.3. 4:_home_ecohen_public_export_ engine_storage_195_iscsi-dc_ export mount.nfs: Connection timed out but - when trying to run the mount command again, with the exact same mount source and mount target, but without any additional parameter, it succeeded (after ~10 seconds): [root@localhost vdsm]# /usr/bin/mount 10.18.57.137:/home/ecohen/ public/export/engine/storage/ 195/iscsi-dc/export /rhev/data-center/mnt/10.18. 57.137:_home_ecohen_public_ export_engine_storage_195_ iscsi-dc_export
My guesss its NFSv3 vs NFSv4
Joop
______________________________ _________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/ mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi Bob,
So the most general case I've found is to stick with v3, but make sure the firewall is properly configured on the storage server (or turn it off).
I configured the firewall on my storage server according to the instructions in [1]. before that, the 'mount' command always failed for me, with/without flags...
NFSv4: requires no firewall configuration (although I thought oVirt handled this automatically - did you change your firewall config after host-deploy?)
did I change my firewall config on my Host, you mean (i.e. the storage client)? I thought that it didn't matter (i.e. only storage *server* firewall proper configuration is important)? but in any case: after deploying my Host, I haven't touched the firewall on the Host, or on the storage server. Maybe I've configured the NFS export path incorrectly within the "/etc/exports" file on my storage server? This is how it appears now: --- /path/to/export *(rw,sync) --- maybe I am missing some parameter(s) to allow it to work properly with v3? Thanks! ---- Regards, Einav [1] http://www.cyberciti.biz/faq/centos-fedora-rhel-iptables-open-nfs-server-por... [some adjustments were needed, e.g. replacing occurrences of 'RH-Firewall-1-INPUT' with 'INPUT', etc.] ----- Original Message -----
From: "Bob Doolittle" <bob@doolittle.us.com> To: "Einav Cohen" <ecohen@redhat.com> Cc: "users" <users@ovirt.org> Sent: Wednesday, December 11, 2013 12:18:21 PM Subject: Re: [Users] add NFS storage domain fails on mount timeout via ovirt
Be aware that I've also had issues where v4 failed but v3 worked. This happened when trying to export storage from the non-root partition. v4 is fussier in that regard although I'm sure it's configurable somehow.
So the most general case I've found is to stick with v3, but make sure the firewall is properly configured on the storage server (or turn it off).
In summary, the advantages (I've found) of each:
NFSv3: requires no NFS configuration to export storage from non-root partitions (useful if you might want to upgrade your OS some day, although oVirt will have to deliver the feature for importing existing domains simply).
NFSv4: requires no firewall configuration (although I thought oVirt handled this automatically - did you change your firewall config after host-deploy?)
Good luck, Bob
On 12/11/2013 12:02 PM, Einav Cohen wrote:
Thanks Bob/Joop - checking the "Override Default Options" checkbox and selecting "V4" in the "NFS Version" drop-down within the "Advanced Parameters" section before hitting "OK" in the 'New Domain' dialog did the trick.
---- Regards, Einav
----- Original Message -----
From: "Bob Doolittle" <bob@doolittle.us.com> To: "Joop" <jvdwege@xs4all.nl> Cc: "users" <users@ovirt.org> Sent: Wednesday, December 11, 2013 11:20:01 AM Subject: Re: [Users] add NFS storage domain fails on mount timeout via ovirt
Yes. In my experience when v4 works and v3 does not it's because of firewall issues on the server.
-Bob On Dec 11, 2013 11:17 AM, "Joop" < jvdwege@xs4all.nl > wrote:
Einav Cohen wrote:
Hi, When trying to add an NFS Export domain via oVirt-engine, it fails on "Problem while trying to mount target". when checking the vdsm.log, it seems that the problem is mount time-out. when I tried to manually run the mount command, in the exact same manner as vdsm, it indeed failed on Connection timed out after ~3 minutes or so: [root@localhost vdsm]# /usr/bin/mount -t nfs -o soft,nosharecache,timeo=600, retrans=6,nfsvers=3 1.2.3.4:/home/ecohen/public/ export/engine/storage/195/ iscsi-dc/export /rhev/data-center/mnt/ 11.2.3. 4:_home_ecohen_public_export_ engine_storage_195_iscsi-dc_ export mount.nfs: Connection timed out but - when trying to run the mount command again, with the exact same mount source and mount target, but without any additional parameter, it succeeded (after ~10 seconds): [root@localhost vdsm]# /usr/bin/mount 10.18.57.137:/home/ecohen/ public/export/engine/storage/ 195/iscsi-dc/export /rhev/data-center/mnt/10.18. 57.137:_home_ecohen_public_ export_engine_storage_195_ iscsi-dc_export
My guesss its NFSv3 vs NFSv4
Joop
______________________________ _________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/ mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On 12/11/2013 02:12 PM, Einav Cohen wrote:
NFSv4: requires no firewall configuration (although I thought oVirt handled this automatically - did you change your firewall config after host-deploy?) did I change my firewall config on my Host, you mean (i.e. the storage client)? I thought that it didn't matter (i.e. only storage *server* firewall proper configuration is important)?
No, I meant the storage server. In my case I use my Node as the storage server, so host-deploy would configure the firewall for me. If you're using a separate storage server it will require manual configuration. Just as a sanity-check I'd probably try disabling the firewall temporarily on your storage server, and see if it starts working with v3. If not it's clearly something else. There could be other issues which v4 addresses which could cause issues with v3 - firewall is just the one I've run into :). As long as you're not concerned about non-root-partition exports you're probably fine as-is (although I thought v4 support was still experimental? If not, why isn't it the default?). Cheers, Bob
----- Original Message ----- From: "Bob Doolittle" <bob@doolittle.us.com> Sent: Wednesday, December 11, 2013 2:32:48 PM
On 12/11/2013 02:12 PM, Einav Cohen wrote:
NFSv4: requires no firewall configuration (although I thought oVirt handled this automatically - did you change your firewall config after host-deploy?) did I change my firewall config on my Host, you mean (i.e. the storage client)? I thought that it didn't matter (i.e. only storage *server* firewall proper configuration is important)?
No, I meant the storage server. In my case I use my Node as the storage server, so host-deploy would configure the firewall for me. If you're using a separate storage server it will require manual configuration. Just as a sanity-check I'd probably try disabling the firewall temporarily on your storage server, and see if it starts working with v3. If not it's clearly something else.
Hi Bob, I disabled the firewall on my storage server and attempted to add another storage domain on the same storage server with v3 - it succeeded. to further verify - I then enabled the firewall again and attempted to add yet another storage domain with v3 - and it failed, just like before. so it seems that you are right - something is probably wrong with the firewall configuration on my storage server - I will investigate. Many Thanks!
There could be other issues which v4 addresses which could cause issues with v3 - firewall is just the one I've run into :). As long as you're not concerned about non-root-partition exports you're probably fine as-is (although I thought v4 support was still experimental? If not, why isn't it the default?).
Cheers, Bob
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (3)
-
Bob Doolittle -
Einav Cohen -
Joop