Re: File permission issues, lost of question marks in shared folder

[Ben Ellis]

That doesn't work for me, I do that and it has no effect. I'd be happy to find some solution that wasn't as cumbersome as having to do vagrant reload. It would be great if vagrant could implement sshfs as an alternative to virtual box's buggy shared folder.

On Tuesday, August 21, 2012 10:20:53 PM UTC+2, Adam Wisniewski wrote:

I've been reloading Vagrant to fix this issue. Today I discovered that just remounting the mount within the guest works as well.

sudo mount /vagrant -o remount

On Sunday, 1 July 2012 08:40:25 UTC-4, Ben Ellis wrote:

I see this same behavior. I've tried using the nfs option, but I still get the same issue. I've also tried disabling the shared folder and using sshfs instead. That avoids this issue (as well as the problem of not being able to create symlinks w/in the guest that cross filesystem btw the shared folder and other directories), but I've ran into other issues with sshfs.

A (tiresome) workaround is to reload vagrant, when it starts up the second time, the content you'd created from host that was showing up w/ question marks will now be loaded correctly. Or else wherever possible make a habit of creating files/dirs from the guest instead of the host.

I did some reading up on this issue a while back and, from what I recall, this is an issue with Virtual Box and how it implements shared folders, not a problem with Vagrant.

On Monday, June 4, 2012 8:50:02 PM UTC+2, aventurella wrote:

I get this issue on both mac and win.  The guest OS is ubuntu 12.04.

I can create a new folder or file in the shared space between the host and guest... for example:

config.vm.share_folder "www", "/var/www/test", "./www"

So if I create a new folder or file from my host os in the ./www folder, on the guest side it will show up like this:

?????????? ? ?       ?            ?            ? test_file.txt

?????????? ? ?       ?            ?            ? test_sub_dir

My host OS sees the files just fine, but if I try to make an http request, I will get a file not found. (I have apt-get install apache2'd and the server is running and serves files).

If, on the guest OS side I do something like this:

echo "hello" > guest.txt 

Then I make a http request request for the resource created on the guest side, it will work, the host OS sees the new file as well.

Has anyone seen this behavior before?

Something obvious I am missing?

 

[Kevin Meredith]

Hi aventurella -

Did you resolve this issue?

If so, can you please share what you did?

[r....@portbase.com]

I had a similar problem. 

The cause was that filenames on my host OS (Windows) exceeded some maximum length.

All files that were shorter were correctly mounted with correct owner & permissions.

Howevere those that were too long showed up like this in the vagrant synced folder: