Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Typo in /etc/exports #2169

Closed
x3rAx opened this issue Sep 9, 2013 · 4 comments
Closed

Typo in /etc/exports #2169

x3rAx opened this issue Sep 9, 2013 · 4 comments

Comments

@x3rAx
Copy link

x3rAx commented Sep 9, 2013

When using nfs, I'm getting the following error:

Preparing to edit /etc/exports. Administrator privileges will be required...
nfsd not running
 * Exporting directories for NFS kernel daemon...
exportfs: /etc/exports:1: unknown keyword "no_subtree"
                                                            [fail]
[probearbeit_vm] Mounting NFS shared folders...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mount -o 'vers=3,udp' 192.168.1.1:'/path/on/host' /path/on/vm

Stdout from the command:



Stderr from the command:

stdin: is not a tty
mount.nfs: requested NFS version or transport protocol is not supported

As you can see, there is an error in /etc/exports:

exportfs: /etc/exports:1: unknown keyword "no_subtree"

My /etc/exports looks like this:

# VAGRANT-BEGIN: 1000 fe2868fb-c581-44f4-8ce5-e453756e55ad
/path/on/host 192.168.1.100(rw,no_subtree,check,all_squash,anonuid=1000,anongid=1000,fsid=1916728648)
# VAGRANT-END: 1000 fe2868fb-c581-44f4-8ce5-e453756e55ad

the typo is here: "no_subtree,check".
It must instead be "no_subtree_check

@mitchellh
Copy link
Contributor

Fixed in git already. Thanks!

@julianlam
Copy link

Looks like this fix wasn't in v1.3.1... every time I run vagrant up, it seems to change /etc/exports back to the typo'd version. Is there a workaround until a new version is released?

@x3rAx
Copy link
Author

x3rAx commented Sep 10, 2013

@julianlam: as @mitchellh sayed, it is already fixed in git and will be in the next version (1.3.2) ;)

You cold

  • disable nfs in your Vagrantfile until it is fixed
  • use version 1.2.7 until 1.3.2 is out
  • or fix it yourself: 693b813

@julianlam
Copy link

Thanks! I've already done the third option and updated host.rb.

@ghost ghost locked and limited conversation to collaborators Apr 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants