Here is a thread that goes nowhere of people talking about the same issue. People end up just clearing out their exports or commenting it out.
https://github.com/mitchellh/vagrant/issues/1744 On Wednesday, October 22, 2014 11:14:17 PM UTC-5, David S wrote: > > I keep getting nfs conflicts if i have nfs shares using the same > directories. > > I often have these as nfs shares. > "/Users/username/Code", "/home/vagrant/code". > > If i run one vagrant box...it add this to my exports. > # VAGRANT-BEGIN: 501 5b85e6ec-04ac-4b0d-b7cd-a36b57a39bdd > "/Users/username/Code" 192.168.22.10 -alldirs -mapall=501:20 > # VAGRANT-END: 501 5b85e6ec-04ac-4b0d-b7cd-a36b57a39bdd > > Then when I suspend or halt that one and run another one. It gives me a > conflict error. In order for me to fix this, i have to remove the > conflicting share and do vagrant reload. > > 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.10.1:'/Users/username/Code/app' > /home/vagrant/app > Stdout from the command: > Stderr from the command: > stdin: is not a tty > mount.nfs: access denied by server while mounting > 192.168.10.1:/Users/username/Code/app > > > On Tuesday, October 21, 2014 5:24:19 PM UTC-5, David Salazar wrote: >> >> So I was shocked to realize that vagrant doesn't cleanup its exports to >> nfs via /etc/exports when I halt the machine. Is this expected or normal >> behavior. Is there anyway I can make vagrant clean it up so that when i >> halt it and launch another vagrant setup that uses nfs there aren't any >> conflicts with nfs shares. I have to do this manually right now. >> > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
