Filesystem problems between host and VM.

18 views
Skip to first unread message

Ash Christopher

unread,
Jan 29, 2015, 10:59:59 AM1/29/15
to vagra...@googlegroups.com
I am having an issue where changes on my host machine are not reflected immediately on the VM filesystem. This makes it especially difficult when commit code - the VM will only recognize a subset of changes.

I can force the VM to recognize the changes to files by running `touch /vagrant/path/to/file` but that's not really a good solution. Has anyone else seen this problem before?

Sometimes the lag between when the change is made on the host until it is reflected on the VM filesystem can be measured in minutes.

I originally suspected a time/ntp issue, but I have ensured that the host and the VM times are set correctly, and stay in sync.

Anyone else run across this?

Alvaro Miranda Aguilera

unread,
Jan 29, 2015, 3:39:48 PM1/29/15
to vagra...@googlegroups.com
Hello, 

Not sure what virtualization are you using, but that is typical what you see with Virtualbox filesystem.

I am afraid that due not being a real filesystem, the guest have those problems with files that change often.

What OS are you using on both, host and guest?

Thanks,
Alvaro.

Ash Christopher

unread,
Jan 29, 2015, 3:42:43 PM1/29/15
to vagra...@googlegroups.com
The host is OSX (10.10.1) and the VM OS is Centos5.

Ash Christopher
Director of Engineering



Join us on Twitter: https://twitter.com/WaveHQ
Find us on Facebook: facebook.com/WaveHQ

--
You received this message because you are subscribed to a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/UgINc-ppptU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Alvaro Miranda Aguilera

unread,
Jan 29, 2015, 3:48:12 PM1/29/15
to vagra...@googlegroups.com
Hello,

Try NFS.


the only restriction that I am aware of, is to not share nested path

say on one VM

/path/projects/

and in other

/path/projects/project_awesome

other than that, it should work.



--
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 vagrant-up+...@googlegroups.com.

Ash Christopher

unread,
Jan 29, 2015, 3:55:34 PM1/29/15
to vagra...@googlegroups.com
We are using NFS, rather than VBFS.

In our Vagrant file, we have the following:

config.vm.synced_folder ".", "/vagrant", :nfs => conf['nfs'], :nfs_version => "3,nolock,udp"

Ash Christopher
Director of Engineering



Join us on Twitter: https://twitter.com/WaveHQ
Find us on Facebook: facebook.com/WaveHQ

Alvaro Miranda Aguilera

unread,
Jan 29, 2015, 4:07:37 PM1/29/15
to vagra...@googlegroups.com
Ah, I miss that part somehow, sorry.

on this issue ticket are some mountpoint options in case you want to have a look:


Reply all
Reply to author
Forward
0 new messages