-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
shared folder problem #351
Comments
This same thing has happened to me. OH GOD, this is so frustrating. I'm going to ask a co-worker how we fixed this tomorrow (if we even did). This was so dumb. |
We fixed it using NFS. On Ubuntu: This has to be done both on the host and in your box. Since you can't do it via provisioning, you may have to re-package the box. |
@mitchellh Any idea yet? |
Yes, this has been solved. This is due to a bug/issue with the
Or if you use nginx:
Yay! |
Ah, is this solvable in vagrant too, or is this something virtualbox has to fix? |
This is something VirtualBox has to fix, unfortunately. For now, please use the proper configuration option for your servers. |
Ok, just wanted to be sure. Sorry to keep asking questions, but any idea if they are tracking this? |
till, I wasn't able to find any tickets... Mitchell |
Adding a link for completeness: http://www.virtualbox.org/ticket/9069 |
I lost a ████ing hour and a half to this nonsense. Any thoughts on how this could be automatically detected? A scan of /etc/nginx.conf for |
I'd be a bit worried that Vagrant scanning nginx or apache configs would be doing too much. There are various ways that this could surface, and it really is up to VirtualBox to fix this issue. I realize it is frustrating (I too spent hours until I stumbled upon the answer), but I think that adding this to Vagrant would not be correct. |
Sure, I understand. How about some documentation? Two good places: http://vagrantup.com/v1/docs/config/vm/share_folder.html |
I think the shared folder documentation would be a good place to put a warning. The docs are open source in the |
PR'd: #1154 |
The bug in VirtualBox still seems to be present, but in the new documentation for synced_folders the note about sendfile seems to have been dropped. |
@mitchellh Would it be possible to put a blurb about this in the new docs? I noticed it is in the v1 documentation but missing from the new docs. Just spent a few hours banging my head against the wall here as well. |
Virtualbox has a bug that could cause static files to not update and seem cached. References: * http://wiki.nginx.org/Pitfalls (Virtualbox section) * http://jeremyfelt.com/code/2013/01/08/clear-nginx-cache-in-vagrant/ * hashicorp/vagrant#351 (comment)
because vagrant inherit bug from virtualbox regarding shared folders in some point it could corrupt files. When you change a file on/in a shared folder, the change is not seen when through a webserver (e.g. nginx). for more info: hashicorp/vagrant#351 (comment) ticket at VB: https://www.virtualbox.org/ticket/9069
There is another VirtualBox ticket here for this same issue. It all seems to be being ignored. :-( |
I had the same issue and tried NFS. NFS possibly corrupted my git index. I had an error similar to this: http://stackoverflow.com/questions/4254389/git-corrupt-loose-object Not sure where it came from exactly as I just booted up to find that error, though this coincides with the first time I used NFS. |
Please add the information about Virtualbox send file bug on: http://docs.vagrantup.com/v2/synced-folders/nfs.html. |
@mitchellh |
Still no solution for this bug? I need to use x-sendfile module in my project and EnableSendfile on is mandatory :| |
If I add "sendfile off;" to my config the consistency issues are solved, but page loads where a lot of static files are served become extremely slow. They go from 1s to 12s. Has anyone else had the same problem? |
sendfile is a feature to speed things up, and it's broken, so it's pretty normal that things slow down (but work correctly) when you turn it off, although it wasn't as extreme a slowdown for me as it was for you. I found it very interesting that performance increased a ton when I upgraded from boot2docker 1.7 to boot2docker 1.8. Boot2docker bundles their own version of VirtualBox, so I'm wondering if there was something changed there that affected things. |
- Added a Dreambox Message of the Day (motd) - Fixed an issue preventing sites from displaying when accessed via IP address - Added compiled package files - Cleaned up documentation (more to come...) - Disabled Sendfile [hashicorp/vagrant#351 (comment)](hashicorp/vagrant#351 (comment)) - Fixed broken MySQL build script - Restructured source files and development workflow - Fixed PROJECT_ROOT variable used by `user_setup` - Updated broken package source URLs - Enabled and loaded shared Apache modules
I know this is closed, but non of these fixed my issue. Turns out I also had to update gunicorn to not use sendfile. |
This is far from being a solved issue. I'm running a Golang webserver using Vagrant, modified a .css file but the changes are not visible until doing a |
According to latest status https://www.virtualbox.org/ticket/9069 this should be fixed in VirtualBox 6.0.6, can anyone that knows how to easily reproduce the issue confirm the fix? |
It is not fixed for me, VirtualBox 6.0.14 running Ubuntu Xenial on 4.4.0 Kernel
The only way is to not use sendfile for shared folders until it's fixed. I don't know Goland, but that https://github.com/wader/disable_sendfile_vbox_linux might be helpful. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
We've run into weird inconsistency issues with shared folders.
This is the configuration in
Vagrantfile
:When I edit a file on the share -- either by
vagrant ssh
into the VM and editing directly, or on the host system -- I can see the change done to a file when Icat foo
, etc.. However, it gets tricky when this file is a static asset served by nginx. So no matter what I do, the state of the file is not refreshed and the content delivered is the same as when I started the VM (vagrant up
). To refresh the file I have to either rename it permanently, orvagrant destroy && vagrant up
.My nginx configuration is pretty generic. The reason why I rule out nginx is, that I ran into someone with the same issue, and he's using a
share_folder
in Vagrant as well.I found this issue in
0.6.9
and also0.7.3
.Supposedly this works better when an NFS export is used. I'm testing this next.
The text was updated successfully, but these errors were encountered: