NFS server for windows(winnfsd.exe) still running after vagrant halt

[pablobb]

Is there an option to stop winnfsd.exe after vagrant machine has stopped ?

[marcharding]

Currently not. You can always kill it manually though...

[vbarzokas]

That causes issues if you do vagrant halt and then again vagrant up.
I get a lot of errors when trying to perform simple operations on the mounted files, like this one rm: cannot remove '<FILENAME>': Input/output error

So I always have to remember shutting down the winnfsd.exe too with
vagrant halt && taskkill /f /im winnfsd.exe

[leandrocrs]

As a workaround, open Powershell as Admin, then enter the following command:

Get-Process winnfsd* | select Id | Stop-Process

[sven-carstens]

As there is no real hook with the nfs capability that gets called on shutdown we would need to hook machine_action_halt and work from there.

• Remove nfs entries for the current machine from the nfspaths file (you could have multiple instances running)
• If that file is empty afterwards stop the winnfsd

[jkrasniewski]

Currently this can be easily solved using vagrant triggers:

  config.trigger.after :halt do |trigger|
    trigger.info = "Clean all nfs processes"
    trigger.run = {inline: "taskkill /IM \"winnfsd.exe\" /F ; exit 0"}
    trigger.on_error = :continue
  end