Skip to content
This repository has been archived by the owner on Feb 13, 2023. It is now read-only.

Latest nfs-utils doesn't work out of the box with Vagrant #1468

Closed
3 of 4 tasks
oxyc opened this issue Jul 6, 2017 · 6 comments · Fixed by #1482
Closed
3 of 4 tasks

Latest nfs-utils doesn't work out of the box with Vagrant #1468

oxyc opened this issue Jul 6, 2017 · 6 comments · Fixed by #1482

Comments

@oxyc
Copy link
Collaborator

oxyc commented Jul 6, 2017

Issue Type

  • Bug Report / Support Request

Summary

As of nfs-utils-2-1-2-rc2 (discussion) UDP is disabled by default thus requiring the user to either:

  1. enable udp in /etc/nfs.conf
  2. change the nfs options in Drupal VM's 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.

  • Ubuntu 16.04: UDP enabled nfs-utils v1.2.8 ref
  • Fedora 25, 26: UDP disabled nfs-utils v2.1.1-5.rc4+ ref
  • Arch Linux: UDP enabled nfs-utils v2.1.1-4 ref
  • Debian 9: UDP enabled nfs-utils v 1.3.4-2.1 ref

I 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:

   if options[:type] == 'nfs' && !options.key?(:nfs_version) && Vagrant::Util::Platform.linux?
     options[:nfs_version] = 4
     options[:nfs_udp] = false
   end

Related:

@oxyc
Copy link
Collaborator Author

oxyc commented Jul 6, 2017

@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?

@oxyc
Copy link
Collaborator Author

oxyc commented Jul 18, 2017

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.

@oxyc
Copy link
Collaborator Author

oxyc commented Jul 18, 2017

An employee at HashiCorp also recommended my latest suggestion when using intense composer installs hashicorp/vagrant#7799 (comment)

@oxyc
Copy link
Collaborator Author

oxyc commented Jul 20, 2017

Anyone on Linux who has had this issue, would be great if you could check if #1482 solves it.

@jozzya
Copy link

jozzya commented Jul 21, 2017

This looks very similar to the issue I had with Fedora 25.
#245 (comment)

@oxyc
Copy link
Collaborator Author

oxyc commented Jul 21, 2017

@jozzya yes that's the same issue. I'm now leaning more towards defaulting to TCP because

  • There's been a ton of random NFS bugs triggered during intense composer operations on Linux lately, all seem to be fixed by switching to TCP
  • There's really no reason to use UDP unless it's faster, which it doesnt seem to be.

Any chance you could test the PR #1482 and see if it works on Fedora?

geerlingguy added a commit that referenced this issue Jul 27, 2017
Issue #1468: Fix various Linux issues with NFS by defaulting to TCP
ashabed pushed a commit to debugacademy/academyvm that referenced this issue Jan 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants