-
-
Notifications
You must be signed in to change notification settings - Fork 647
Latest nfs-utils
doesn't work out of the box with Vagrant
#1468
Comments
@yareckon mind sharing why you changed the nfs version? Was it because it didn't work out of the box, or something else? @quietone1 did you have the default nfs-utils package or had you updated it manually or done other config configurations? I'm wonder why nfsv3 with udp didn't work for you on Debian Jessie. @larmedina75 you mentioned you were using nfsv4, was this the default on your distro? Which distro are you using? |
I don't think we actually need to specify NFSv4, we could just let the default be used but set it to use TCP rather than UDP. This works on macOS sierra too and even gives a performance improvement for me. |
An employee at HashiCorp also recommended my latest suggestion when using intense composer installs hashicorp/vagrant#7799 (comment) |
Anyone on Linux who has had this issue, would be great if you could check if #1482 solves it. |
This looks very similar to the issue I had with Fedora 25. |
@jozzya yes that's the same issue. I'm now leaning more towards defaulting to TCP because
Any chance you could test the PR #1482 and see if it works on Fedora? |
Issue #1468: Fix various Linux issues with NFS by defaulting to TCP
Issue Type
Summary
As of
nfs-utils-2-1-2-rc2
(discussion) UDP is disabled by default thus requiring the user to either:/etc/nfs.conf
config.yml
At the moment this only affect Fedora 25+ but we have had issues regarding this before. Not sure what prompted them then as the the repo sources do specify versions that should have udp and nfsv3 support.
Some
nfs-utils
versions across distros.nfs-utils v1.2.8
refnfs-utils v2.1.1-5.rc4+
refnfs-utils v2.1.1-4
refnfs-utils v 1.3.4-2.1
refI think it's still fairly safe to default to nfsv4 on Linux hosts as they mention in the commit that it's been supported for a decade. A possible fix:
Related:
The text was updated successfully, but these errors were encountered: