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

Mounting problem on Windows 8.1 #12

Open
billmn opened this Issue Jun 10, 2014 · 84 comments

Comments

Projects
None yet
@billmn

billmn commented Jun 10, 2014

I'm using Laravel Homestead box ( http://laravel.com/docs/homestead ) and your awesome plugin to allow NFS on WIndows 8.1 Pro but I have some problem on mounting folders.

I've changed this line to force to use NFS on Windows https://github.com/laravel/homestead/blob/master/scripts/homestead.rb#L45

But when I run "vagrant up" I see this:
nfs_error

Thoughts?

@GM-Alex

This comment has been minimized.

Member

GM-Alex commented Jun 10, 2014

Disable your firewall and check if the winnfsd process is running.

@billmn

This comment has been minimized.

billmn commented Jun 10, 2014

I've disabled Windows Firewall and checked task manager ... winnfsd.exe (32bit) running.

But the error is the same

@GM-Alex

This comment has been minimized.

Member

GM-Alex commented Jun 10, 2014

You could login to your box and try to run the command mount -o 'vers=3,udp,nolock' 192.168.10.5:'/C/www/projects' /home/vagrant/Code manually and play with the parameters like

mount -o 'vers=2,udp,nolock' 192.168.10.5:'/C/www/projects' /home/vagrant/Code
mount -o 'vers=3,nolock' 192.168.10.5:'/C/www/projects' /home/vagrant/Code
mount -o 'vers=4,udp,nolock' 192.168.10.5:'/C/www/projects' /home/vagrant/Code

@billmn

This comment has been minimized.

billmn commented Jun 11, 2014

I've tried some commands on Ubuntu ... here commands responses:
cmd_resp

@billmn

This comment has been minimized.

billmn commented Jun 12, 2014

Oh I forgot to specify what I use:

Vagrant 1.6.3 and VirtualBox 4.3.12 r93733

Host Machine: Windows 8.1 Pro x64
Guest Machine: Ubuntu Ubuntu 14.04

@GM-Alex

This comment has been minimized.

Member

GM-Alex commented Jun 20, 2014

Could you search for the batch file nfsservice.bat and change the line

start "" "%~dp0winnfsd" -log off -pathFile %2 -id %3 %4

to

start "" "%~dp0winnfsd" -log on -pathFile %2 -id %3 %4

That will keep the window for the nfs daemon open and we can see what happens.

@borisschapira

This comment has been minimized.

Contributor

borisschapira commented Jun 20, 2014

I did that, modified my VagrantFile nfs_setting condition to :

nfs_setting = RUBY_PLATFORM =~ /darwin/ || RUBY_PLATFORM =~ /linux/ || Vagrant.has_plugin?("vagrant-winnfsd")

and launched vagrant up.

The process freezes on

==> default: Mounting NFS shared folders
@GM-Alex

This comment has been minimized.

Member

GM-Alex commented Jun 20, 2014

@borisschapira And than you get a timeout?

@borisschapira

This comment has been minimized.

Contributor

borisschapira commented Jun 20, 2014

@GM-Alex Nope, nothing. I tried to relaunch, same issue. 4 minutes waiting, still counting.

@GM-Alex

This comment has been minimized.

Member

GM-Alex commented Jun 20, 2014

Could you try to switch the logging on as suggested above and post the output? Do you have the firewall rules set up correctly?

@borisschapira

This comment has been minimized.

Contributor

borisschapira commented Jun 20, 2014

My guest is a Debian :

Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.46-1

And here is what I got, executing the first command :

windows powershell

@borisschapira

This comment has been minimized.

Contributor

borisschapira commented Jun 20, 2014

And then I got the same message than @billmn 10 days ago.

@GM-Alex

This comment has been minimized.

Member

GM-Alex commented Jun 20, 2014

Oh there was a : missing, I changed the comment above. But could you please change also the nfsservice.bat (search for it on your windows machine) file.

@borisschapira

This comment has been minimized.

Contributor

borisschapira commented Jun 20, 2014

Ok, so let's try again :

  1. I've created a www folder inside C:, with my project files
  2. I've relaunched vagrant up, I've got the freeze described above
  3. I've logged myself in, and tried :
sudo mount -o 'vers=3,udp,nolock' 192.168.10.5:'/C/www/' /var/www/

Response :

mount.nfs: Connection timed out
  1. I've tried again, with -v for verbose mode :
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Fri Jun 20 13:47:24 2014
mount.nfs: trying text-based options 'vers=3,udp,nolock,addr=192.168.10.5'
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Timed out
mount.nfs: trying text-based options 'vers=3,udp,nolock,addr=192.168.10.5'
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Timed out
...
@borisschapira

This comment has been minimized.

Contributor

borisschapira commented Jun 20, 2014

I forgot to write it by playing with the parameters did not work either.
Maybe I did not understand. For example, where does the 192.168.10.5 IP come from ? Maybe I should change it by another...

@GM-Alex

This comment has been minimized.

Member

GM-Alex commented Jun 20, 2014

Could you please update to version 1.0.8, turn on the logging of the module as described in the readme and paste the output of the winnfsd daemon window.

@borisschapira

This comment has been minimized.

Contributor

borisschapira commented Jun 21, 2014

I've updated ton version 1.0.8 and added to my VagrantFile

config.winnfsd.logging = "on"

How can I display the winnfsd daemon window ? A vagrant up is not showing any additionnal window, it only freezes as usual...

@borisschapira

This comment has been minimized.

Contributor

borisschapira commented Jun 21, 2014

I looked inside the nfsservice.bat and I think there is an issue.
I tried a nfsservice.bat start command.
Output :

:==winnfsd.exe était inattendu.

(my system is in french, "était inattendu" means "unexpected")

I did not understand the message, si I played with the script, echoing %result% juste before the line

if %1==status (

Output :

information :
:==winnfsd.exe était inattendu.

As you can see, my %result% end with a : and contains a space. I think it can make the evaluation below erroneous. So I tried a simpler version of the script 👍

@echo off

:: Fancy way to enable command extensions, where available
:: http://technet.microsoft.com/en-us/library/bb491001.aspx OR http://www.robvanderwoude.com/allhelpw2ksp4_en.php#SETLOCAL
verify other 2>nul
    setlocal enableextensions
    if errorlevel 1 echo Unable to enable command extensions

for /f "tokens=1 delims= " %%y in ('tasklist /nh /fi "imagename eq winnfsd.exe"') do @set result=%%y


if %result%==winnfsd.exe (
    echo "It worked !"
)

exit 1

And the output was :

:==winnfsd.exe était inattendu.

So I think I've nailed an issue, haven't I ?

@borisschapira

This comment has been minimized.

Contributor

borisschapira commented Jun 21, 2014

I think that you should put " around your strings variable when evaluating. This works :

@echo off

:: Fancy way to enable command extensions, where available
:: http://technet.microsoft.com/en-us/library/bb491001.aspx OR http://www.robvanderwoude.com/allhelpw2ksp4_en.php#SETLOCAL
verify other 2>nul
    setlocal enableextensions
    if errorlevel 1 echo Unable to enable command extensions

for /f "tokens=1 delims= " %%y in ('tasklist /nh /fi "imagename eq winnfsd.exe"') do @set result=%%y


if "%result%"==winnfsd.exe (
    echo "Winnfsd is started"
) else (
    echo "Winnfsd is not started"
)

exit 1
@borisschapira

This comment has been minimized.

Contributor

borisschapira commented Jun 21, 2014

With the modification above, the Mounting do not freeze anymore and the NFS daemon window is launched.
When I try to access some files, the NFS deamon shows me a lot of NFS LOOKUP, NFS ACCESS, NFS GETATTR... so I think it works !

@borisschapira

This comment has been minimized.

Contributor

borisschapira commented Jun 21, 2014

The nfsservice.bat did not worked well without quotes on both sides of the ===, telling me winnfsd.exe was not running when he was.

@borisschapira

This comment has been minimized.

Contributor

borisschapira commented Jun 21, 2014

With the file contributed as above, I changed my config to

config.winnfsd.logging = "off"

My vagrant up output is now :

==> default: Configuring and enabling network interfaces...
==> default: Exporting NFS shared folders...
==> default: Preparing to edit nfs mounting file.
[NFS] Status: halted
[NFS] Start: started
==> default: Mounting NFS shared folders...
==> default: Mounting shared folders...
    default: /vagrant => C:/Users/Boris/Documents/GitHub/aquitaine
==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> default: to force provisioning. Provisioners marked to run always will still run.

Isn't that very good 👍 ?

@borisschapira

This comment has been minimized.

Contributor

borisschapira commented Jun 26, 2014

Now that I've managed to host a CentOS, I'm trying to host an Ubuntu 12.03 on Windows 8.1.
It's my only Virtual Machine running.

Here is my VagrantFile Synced folders :

config.vm.synced_folder "salt/roots/", "/srv/", :nfs => not_windows
config.vm.synced_folder "salt/roots/salt/apache2/html-default", "/var/www/html/default/", :nfs => nfs_setting

if Dir.exists?('projects/project1/')
    puts 'Binding projects/project1/' 
    config.vm.synced_folder "projects/project1/", "/var/www/html/project1/", :nfs => nfs_setting
end

I've got the already known issue on vagrant up :

==> default: 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,nolock' 10.0.0.1:'/C/www' /var/www/html/

Stdout from the command:



Stderr from the command:

stdin: is not a tty
mount.nfs: access denied by server while mounting 10.0.0.1:/C/www

So I connected directly to the VM and tried to run the mounting command myself, here is the response :

vagrant@gsoi:~$ sudo mount -o 'vers=3,nolock' 10.0.0.1:'/C/www/projects/project1' /var/www/html/project1 --verbose
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Thu Jun 26 10:06:02 2014
mount.nfs: trying text-based options 'vers=3,nolock,addr=10.0.0.1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 10.0.0.1 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 10.0.0.1 prog 100005 vers 3 prot UDP port 1058
mount.nfs: mount(2): Permission denied
mount.nfs: access denied by server while mounting 10.0.0.1:/C/www/projects/project1

And when I look the winnfsd daemon, I see a list of all known pathes (including the two above) and then :

MNT from 10.0.0.157
Final local requested path: C:\www\salt\roots\salt\apach2\html-default

NFS GETATTR C:\www\salt\roots\salt\apache2\html-default OK

So it seems the first Synced Folder is correctly mounted and there's an issue on the second folder to sync. Am I right ?

@GM-Alex

This comment has been minimized.

Member

GM-Alex commented Jun 26, 2014

New release online. Should be fixed now. @borisschapira Thanks again for your help.

@GM-Alex GM-Alex closed this Jun 26, 2014

@borisschapira

This comment has been minimized.

Contributor

borisschapira commented Jun 27, 2014

@GM-Alex Thank you !

@borisschapira

This comment has been minimized.

Contributor

borisschapira commented Jun 27, 2014

I still have the issue described above but I am not able to tell if the issue is Windows-related or related to the special multi-project configuration that I have.

If you want to test it, here is a complete Vagrant install to test : https://www.dropbox.com/s/dvxb8l47uaagyms/vagrantTest.zip
Extract, and vagrant up --provision

@pgcd

This comment has been minimized.

pgcd commented Jul 18, 2014

I have the same issue - two synced folders, one of which is handled correctly while the other returns an "access denied by server" error.
Please note that, in my case, it's a sibling folder - the Vagrantfile is in workspace/A (which mounts correctly) and the second folder is workspace/B.

@borisschapira

This comment has been minimized.

Contributor

borisschapira commented Jul 18, 2014

@GM-Alex Maybe you should reopen the issue, or make a new one for that "multiple folders" thing...
My issue and the one of @pgcd seems to be the same...

## First folder, correctly managed
config.vm.synced_folder "salt/roots/", "/srv/", :nfs => nfs_setting

## Other folders, error
if Dir.exists?('projects/mawDevs/')
  config.vm.synced_folder "projects/mawDevs/", "/var/www/maw/", :nfs => nfs_setting
end

(extracted from https://github.com/MakeAWish/mawVagrant/blob/master/Vagrantfile)

@FractalizeR

This comment has been minimized.

FractalizeR commented Mar 2, 2015

No, I didn't, sorry. I don't want to mix my projects like that for now. I corrected my Vagrant script to fall back to VB's internal sharing mechanism when host OS is Windows until this is fixed.

@bleleve

This comment has been minimized.

bleleve commented Mar 3, 2015

Hi there,

I am on Win 8.1 and I was facing the same problem.
I set the compatibilty mode to Windows 8 and it works fine for me too !

Cheers namaless ;)

@borisschapira

This comment has been minimized.

Contributor

borisschapira commented Mar 4, 2015

I've set the compatibility mode. It seems to work nicely for a "one-project" vagrant but as usual, on a multi-project vagrant (as described in june #12 (comment)), that does not work 😢

@pinano

This comment has been minimized.

pinano commented Mar 5, 2015

I am also on Windows 8.1. Even after setting the compatibility mode to Windows 8 I can't get to run more than two machines with an nfs share simultaneously.

If I'm about to start the third machine and I previously kill winnfsd.exe, the folder will mount but, obviously, I will loose the previous two mountpoints of the machines opened previously.

If I then go and vagrant reload the previous two machines, no matter what I do I always end up with a maximum of two nfs working machines. The third one never gets to mount.

Does anybody else have this same issue where they cannot start more than two machines with an nfs share?

@borisschapira

This comment has been minimized.

Contributor

borisschapira commented Mar 5, 2015

@pinano As already mentioned, I cannot mount multiple folders, whether they're on the same or different hosts.

@pinano

This comment has been minimized.

pinano commented Mar 5, 2015

@borisschapira the funny thing is that I can mount up to two folders, whether it is on the same project or in two different projects, but I cannot get to mount the third one. It feels as if it was a limitation of winnfsd somehow, although it doesn't make much sense to me...

@borisschapira

This comment has been minimized.

Contributor

borisschapira commented Mar 5, 2015

@pinano Hum, you're right, it seems that I have the same issue, with two folders but no more.
I was misled by my provisionning configuration, but you're right, I have one provisioning folder and one project folder that mount. It's the second project folder (so, the third folder) that does not work.

What's funny is that when the log is activated with :

if Vagrant.has_plugin?("vagrant-winnfsd")
    config.winnfsd.logging = "on"
end

the third folder appears in the logged NFS requests... same behaviour on your install ?

@nakanaa

This comment has been minimized.

nakanaa commented Mar 5, 2015

I'm having the same problem when using dduportal/boot2docker. WinNFSd window was printing NOTIMP (not implemented) so I tried debugging it today. The message comes from PortmapProg.cpp where the program is waiting for a packet to ask for port mappings.

I found a RFC about the port mapping which says that the correct procedure is PMAPPROC_GETPORT which WinNFSd is waiting for. If it sees something else it discards it and prints NOTIMP. For some reason WinNFSd is only getting PMAPPROC_DUMP at least with dduportal/boot2docker. I then tried to debug it on a chef/debian-7.6 box and to my suprise it was sending PMAPPROC_GETPORT and everything worked fine!

So at least in my case it's something to do with the box itself. At least SMB shares are working with dduportal/boot2docker so I'll stick with that for now.

@pinano

This comment has been minimized.

pinano commented Mar 6, 2015

@borisschapira What happens in my install, once I have been examining the logs, is that it mounts the first folder, then it mounts the second folder, and when I vagrant up the third machine it tries to mount the second folder again instead of the third one.

I am pasting a piece of the winnfsd log to see if it makes sense to anyone. I have replaced the actual folder names with project1, project2 and project3 for the sake of simplicity and to show the order the machines are booted up.

I have also inserted some comments where something relevant is going on:

=====================================================
WinNFSd v2.0
Network File System server for Windows
Copyright (C) 2005 Ming-Yang Kao
Edited in 2011 by ZeWaren
Edited in 2013 by Alexander Schneider (Jankowfsky AG)
=====================================================
Path #1 is: C:\dev\webroot\project2, path alias is: /C/dev/webroot/project2
Path #2 is: C:\dev\webroot\project3, path alias is: /C/dev/webroot/project3
Path #3 is: C:\dev\webroot\project1, path alias is: /C/dev/webroot/project1
Portmap daemon started
NFS daemon started
Mount daemon started
Local IP = 172.28.128.1
Type 'help' to see help

# Vagrant up project1 machine (IP 192.168.56.101) and it mounts project1 folder
PORTMAP GETPORT 100003 2049
NFS NULL OK
PORTMAP GETPORT 100005 1058
MOUNT NULL
MOUNT NULL
MOUNT Path C:\dev\webroot\project2 with path alias  /C/dev/webroot/project2 already known
Path C:\dev\webroot\project3 with path alias  /C/dev/webroot/project3 already known
Path C:\dev\webroot\project1 with path alias  /C/dev/webroot/project1 already known
MNT from 192.168.56.101
Final local requested path: C:\dev\webroot\project1

# Vagrant up project2 machine (IP 192.168.56.201) and it mounts project2 folder
PORTMAP GETPORT 100003 2049
NFS NULL OK
NFS FSINFO C:\dev\webroot\project1  OK
NFS PATHCONF C:\dev\webroot\project1  OK
NFS FSINFO C:\dev\webroot\project1  OK
PORTMAP GETPORT 100003 2049
NFS NULL OK
PORTMAP GETPORT 100005 1058
MOUNT NULL
MOUNT NULL
MOUNT Path C:\dev\webroot\project3 with path alias  /C/dev/webroot/project3 already known
Path C:\dev\webroot\project1 with path alias  /C/dev/webroot/project1 already known
Path C:\dev\webroot\project2 with path alias  /C/dev/webroot/project2 already known
MNT from 192.168.56.201
Final local requested path: C:\dev\webroot\project2

# Vagrant up project3 machine (IP 192.168.56.202) and it tries to mount project2 folder !!!
PORTMAP GETPORT 100003 2049
NFS NULL OK
NFS FSINFO C:\dev\webroot\project2  OK
NFS PATHCONF C:\dev\webroot\project2  OK
NFS FSINFO C:\dev\webroot\project2  OK
PORTMAP GETPORT 100003 2049
NFS NULL OK
PORTMAP GETPORT 100005 1058
MOUNT NULL
MOUNT NULL
MOUNT Path C:\dev\webroot\project1 with path alias  /C/dev/webroot/project1 already known
Path C:\dev\webroot\project2 with path alias  /C/dev/webroot/project2 already known
Path C:\dev\webroot\project3 with path alias  /C/dev/webroot/project3 already known
MNT from 192.168.56.202
Final local requested path: C:\dev\webroot\project2

...

# It tries to mount project2 folder 8 times like shown above and then it fails with a
# mount.nfs: acces denied by server while mounting 192.168.51.1:/C/dev/webroot/project3

@nakanaa The boxes I'm using are all Ubuntu 14.04. Do you suggest switching to Debian to see if the behaviour is any different?

@dave-newson

This comment has been minimized.

dave-newson commented Mar 11, 2015

After some extensive testing, I believe this is a fault with the winnfsd service. vagrant-winnfsd itself isn't to blame, but could be modified to help avoid this problem.

When requesting a mount, winnfsd appears to be comparing the length of the alias, and then comparing the content. If an alias of greater length comes first, it is incorrectly matched as the "final local requested path".

For instance, this works just fine (some stuff omitted):

config.vm.synced_folder "./www", "/data/www"
config.vm.synced_folder "./etc/test", "/data/test"
config.vm.synced_folder "./etc/nginx", "/data/nginx"
config.vm.synced_folder "./etc/t33st", "/data/t33st"

But in the following, a request for /www will result in a match to to /t33st, because it is of greater length and comes first.

config.vm.synced_folder "./etc/t33st", "/data/t33st"
config.vm.synced_folder "./www", "/data/www"
config.vm.synced_folder "./etc/test", "/data/test"
config.vm.synced_folder "./etc/nginx", "/data/nginx"

Additionally, vagrant-winnfsd leaves the winnfsd service running when the vagrant instance is halted.
If you then modify the nfspaths file used by winnfsd, either manually or by changing your Vagrantfile and starting your vagrant instance once more, the previous aliases will remain in memory of winnfsd, but it will still try to pattern match using the content from the nfspaths file.

The end result is a mis-matching alias map, causing all sorts of weird issues that make absolutely no sense. To fix this, simply kill the winnfsd instance if you make any modifications to your shares.

In short, the workarounds are:

  • Ensure your shares are listed in length-ascending order
  • Ensure you kill winnfsd if you modify your shares list

Because of this, it would be an enhancement if:

  • vagrant-winnfsd could write (its own?) nfspaths file, which the paths in length-ascending order.
  • vagrant-winnfsd enforced the restarting of the winnfsd service on vagrant star.

Failing that, someone should go fix winnfsd.

I debugged this in Windows 8.1, turning on logging manually in nfsservice.bat.

@borisschapira

This comment has been minimized.

Contributor

borisschapira commented Mar 12, 2015

@dave-newson thanks for this deep debugging, I will try that ASAP !

@borisschapira

This comment has been minimized.

Contributor

borisschapira commented Mar 12, 2015

@dave-newson I confirm everything you said, now it works.

I've find another temporary solution : declare all my sync folders in an array and reorder the array in length-ascending order before declaring them to vagrant for synchronization : https://github.com/borisschapira/vagrant-template/blob/master/Vagrantfile#L62

Thanks a lot, again.

@FractalizeR

This comment has been minimized.

FractalizeR commented Mar 12, 2015

Will this be included into the core? :)

@AssemAfify

This comment has been minimized.

AssemAfify commented Mar 29, 2015

@dave-newson thanks a lot it works, i just rearranged my shared folder in my homestead.yaml in ascending order according to length and everything work fine

Thanks a lot for all who contributed in this post, specially @borisschapira and plugin author ofcourse

@IbnSaeed

This comment has been minimized.

IbnSaeed commented Apr 11, 2015

@borisschapira Thanks for the fix. Your fix works with my setup for multiple folder sharing in windows 8.1

@bbodenmiller

This comment has been minimized.

Contributor

bbodenmiller commented Apr 20, 2015

Thanks @dave-newson. Hopefully this gets fixed so I don't have to sort my sync folders list.

@majidaldo

This comment has been minimized.

majidaldo commented May 17, 2015

running with win8 compatibility worked for me. weird.

@prograhammer

This comment has been minimized.

prograhammer commented May 26, 2015

For anyone having problems with Laravel Homestead and a Windows host, I've made this Gist here: https://gist.github.com/prograhammer/9493ee04f30dd74e121b
This should help in overcoming all the issues in the whole process (including the winnfsd fixes mentioned here). With this Gist I successfully have Homestead running, being able to use symlinks (ie. for npm install) and overcoming the Windows long file-path character length restriction, and other problems.

@vaske

This comment has been minimized.

vaske commented Jul 28, 2015

I still have this issue on win 8.1 is there any generic solution so far?

@borisschapira

This comment has been minimized.

Contributor

borisschapira commented Jul 29, 2015

@vaske see my comment on 12 Mar : #12 (comment)

You must put your sync folders in alpha/length order. I propose a way to do it in https://github.com/borisschapira/vagrant-template/blob/master/Vagrantfile, L15 to L62.

@mthompson182

This comment has been minimized.

mthompson182 commented Aug 31, 2015

The quick fix for me that works fine

  1. vagrant halt (does not stop the winnfsd.exe)
  2. Go to Task Manager and end the process winnfsd.exe
  3. vagrant up

It works fine after doing this, like dave-newson said, it does not stop the winnfsd.exe when you do a vagrant halt, so I just stop it manually. I never had to do anything with sync folders.

@bdw429s

This comment has been minimized.

bdw429s commented Sep 3, 2015

@borisschapira Must the shares be ordered by the host path or the guest path? Also, if using relative paths, must the expanded path be sorted, or just the relative portion?

If this is a bug in the plugin, is there a dedicated ticket for it somewhere. There are handful of issues related to shared not working but they all have a very large amount of similar comments with no apparent resolution so it's hard to even tell which issues are really for what in this repo.

@borisschapira

This comment has been minimized.

Contributor

borisschapira commented Sep 6, 2015

@bdw429s Host path ("from" : https://github.com/borisschapira/vagrant-template/blob/master/Vagrantfile#L62). I don't understand you relative vs. expanded path question. If the relative path are sorted, the expanded are too because they share the same root...

@zek

This comment has been minimized.

zek commented Sep 26, 2015

I've just changed actimeo=1 to nolock,vers=3,udp and set compatibility to w8.

It works like a charm! I'm using Windows 10 64 bit.

@yannschepens

This comment has been minimized.

Contributor

yannschepens commented Sep 26, 2015

Cool. Really cool

Le sam. 26 sept. 2015 16:28, Talha Zekeriya Durmuş notifications@github.com
a écrit :

I've just changed actimeo=1 to nolock,vers=3,udp and set compatibility to
w8.

It works like a charm! I'm using Windows 10 64 bit.


Reply to this email directly or view it on GitHub
#12 (comment)
.

@amirbilu

This comment has been minimized.

amirbilu commented Oct 14, 2015

I have struggled for few hours with vagrant freezes on "default: Mounting NFS shared folders".
I found out Winnfsd is using port 1058 which was taken by some other process on my machine.

Hope this will save some time for others.

@altmind

This comment has been minimized.

altmind commented Dec 24, 2015

@amirbilu hit the same problem. tcp port 1058 is taken by windows "Policy Agent" service. This service is related to IPSec. net stop PolicyAgent helps

@patricknelson

This comment has been minimized.

Contributor

patricknelson commented May 6, 2016

Dear googler's: For anyone having issues with vagrant freezing on the Mounting NFS shared folders be sure to start vagrant with the --debug flag so you can see exactly why to help debugging.

@dave-newson's fix above works for me (#12 (comment)) in at least allowing me to mount one of my shares as NFS. The remaining shares cannot be mounted. In my case:

config.vm.synced_folder "../websites", "/websites", type: 'nfs' # Shorter alias (second param)
config.vm.synced_folder ".", "/etc/puppet", id: "vagrant-root" # Will not mount as 'nfs'.

Where /etc/puppet uses the default share (in my case vboxsf). Currently I'm unsure if this is because it's declared second (and thus only one can mount) or if it's something else. At this point I've given up 😂

@raupie

This comment has been minimized.

raupie commented Jun 27, 2016

I had issues with the winnfsd process not ending on vagrant-destroy and trying to launch another machine. I found this work around to be very helpful, it implements vagrant triggers.

In vagrantfile...

config.trigger.after :destroy do
info "Destroy winnfsd process"
run "Taskkill /IM winnfsd.exe /F"
end

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment