search

winnfsd / vagrant-winnfsd

Manage and adds support for NFS for Vagrant on Windows.
Other
567 stars 62 forks source link

Mouting problem on windows 7 #63

Open marcioquental opened 9 years ago

marcioquental commented 9 years ago

Hi, i'm getting a mounting error when execute "vagrant up" with shared folder type set to nfs.

This is the error that I'm getting: vagrant_error

If I ssh into the VM and run the same command I'll get the following error: "mount.nfs: access denied by server while mounting 172.28.128.1:/C/Developer/Vagrant/www"

The strange this is, if I comment the "config.vm.synced_folder" line to don't share any folder and next run winnfsd from the windows cmd prompt with command: "winnfsd.exe c:\Developer\Vagrant\www" and ssh into the VM and run "sudo mount -o 'vers=3,nolock,udp' 192.168.1.168:/C/Developer/Vagrant/www /home/vagrant/www" everything works fine. The only thing that changes is the server ip on mount command but on my VagrantFile I have this: config.vm.network "private_network", type: "dhcp" config.vm.synced_folder "../www", "/home/vagrant/www", type: "nfs", mount_options: ["vers=3", "nolock", "udp"]

I've tried everything including turn off firewall, turn off anti virus. What am I doing wrong?

EDIT: I'm using the version 1.7.2 of vagrant.

I've found another relevant thing. I've to say that I'm wrong about what I wrote above. The only way that I can put the nfs to work on my environment is using the winnfsd version of Ming-Yang Kao with these binaries: WinNFSd! but when I was using the version that are located in Users\"user".vagrant.d\gems\gems\vagrant-winnfsd-1.0.11\bin I got the error "mount.nfs: access denied by server while mounting 172.28.128.1:/C/Developer/Vagrant/www". What should I do to put nfs work on windows?

vaske commented 9 years ago

any updates on this one? I'm having same issue

worthwhileindustries commented 9 years ago

make sure if you recently upgraded plugins by vagrant plugin update ... that you kill the service currently running in task manager and try upgrading to vbox 5.0 and vagrant 1.7.4... i have had zero problems lately from most recent plugin update. I am also using Win8.1

vaske commented 9 years ago

@worthwhileindustries thanks for quick update will try to follow up your suggestions.

vaske commented 9 years ago

@worthwhileindustries even after that I have same issue, my vagrant config is like: config.vm.synced_folder 'D:/Project/app', '/srv/app',:nfs=> true config.ssh.pty = true

worthwhileindustries commented 9 years ago

wwi_sa_web.vm.synced_folder "www", "/var/www", type: "nfs"

This is what I'm using. I'm not sure what those other options you have are?

vaske commented 9 years ago

@worthwhileindustries "www" what is that some alias on windows machine or ?

worthwhileindustries commented 9 years ago

no it's just a folder in my project that holds a bunch of websites

vaske commented 9 years ago

@worthwhileindustries but it's from your host (Windows) right?

worthwhileindustries commented 9 years ago

yes www (Windows 8.1 host) -> var/www (CentOS 7 guest)

worthwhileindustries commented 9 years ago

maybe it has something to do with D:/Project/app,.... / slashes? I'm not sure... I don't use drive names. I would use relative if possible or try D:\Project\app

Do these work with regular shares minus the nfs?

vaske commented 9 years ago

@worthwhileindustries in your case 'www' on Windows is what? some folder on C: or somewhere else or alias, symlink?

worthwhileindustries commented 9 years ago

yeah just a regular old folder on C

kevinquillen commented 9 years ago

One of our devs just got this error on Windows 7 with VirtualBox-5.0.0-101573-Win. I am having her downgrade to 4.3.30 to see if it still happens.

vaske commented 9 years ago

I left this one and started using vagrant and so on my mac, this was to frustrating to be solved over there...

kevinquillen commented 9 years ago

Started a brand new VM on another Windows 7 machine, got this very same error.

thePanz commented 9 years ago

Is this issue related to #31?