Bugs with file creation on host

IAkumaI commented 10 years ago

Windows 7.

All works fine, but when I create file on my host machine, this file is...invisible on a virtual pc.

For example, I create file test.txt on the host machine. I can cat test.txt fine. But ls doesn't see this file. And PHP doesn't see this file. But cat still can read this invisible file.

lvancrayelynghe commented 10 years ago

Same problem here. Any update ?

johnathanmdell commented 9 years ago

I have this same, problem.

Windows 8 Vagrant 1.6.5

willmorgan commented 9 years ago

I also have this problem occasionally.

Windows 8.1, Vagrant 1.6.5.

T2L commented 9 years ago

Have the same issue, Windows 7, Vagrant 1.6.5

yannschepens commented 9 years ago

Hello everybody,

It's is a Winnfsd problem.

I got the same issue with CentOS6.5 but not with debian wheezy/jessie (which are my testing OS for winnfsd). The only workaround I have is to edit the file inside the VM to get it visible. But it's not seriously usable. Can you send me yours VM OS.

Grettings,

Yann

lvancrayelynghe commented 9 years ago

Hello Yann,

Got the problem with Laravel Homestead 0.2.0 (Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-30-generic x86_64) on Windows 7, Vagrant 1.6.5

Thanks !

T2L commented 9 years ago

Hi Yann,

I'm using Windows 7 32-bit Home Basic + Vagrant 1.6.5 + VirtualBox 4.3 + Official Ubuntu Server 14.04 LTS (Trusty Tahr) from https://atlas.hashicorp.com/ubuntu/boxes/trusty64

Best, Roman

T2L commented 9 years ago

Also, I've troubleshot this issue a bit.

Any write inside the VM in the shared resource fixes this issue (not only the invisible file itself).

yannschepens commented 9 years ago

Thank you for your information, I gonna check that.

2015-01-27 16:01 GMT+01:00 Roman Paska notifications@github.com:

Also, I've troubleshot this issue a bit (however my C++ skills are quite limited).

Any write inside the VM in the shared resource fixes this issue (not only the invisible file itself).

— Reply to this email directly or view it on GitHub https://github.com/GM-Alex/vagrant-winnfsd/issues/27#issuecomment-71661515 .

Yann Schepens

yann.schepens@gmail.com

dkarlovi commented 9 years ago

I can confirm the issue. Also tested this on the identical guest, but a Linux host (so, native NFS implementation) and it works as expected. Must be a winnfsd issue, I guess we track it at https://bitbucket.org/jankowfsky/winnfsd/?

dkarlovi commented 9 years ago

This seems to be related and got a PR attached yesterday so we might see this fixed.

T2L commented 9 years ago

Any updates on this issue?

philbates35 commented 9 years ago

Hi, I have the exact same issue using Vagrant 1.7.2, Windows 7 host and CentOS 6.6 guest. It would be great to see this resolved, as this is stopping me from making NFS my primary sync folder method. I can provide more information if required, so let me know if that would be helpful and what you need.

jfbibeau commented 9 years ago

Same issue, Windows 7 host with RHEL 6.6 guest. If you need anything, let me know. Doesn't look like the PR is progressing anymore, sadly :(

yannschepens commented 9 years ago

I'm working on, it's a bit long sorry.

jfbibeau commented 9 years ago

Thanks @yannschepens !

n8green commented 9 years ago

Same issue - Windows 7 host, Ubuntu 14.04 guest, Vagrant 1.6.3

HeathNaylor commented 9 years ago

We are having this as well. @yannschepens any idea of when this might be fixed? Is there anything people can do to help you with this? This and other file manipulation issues is preventing our Windows users from really using NFS for the time being.

yannschepens commented 9 years ago

I have the same problems with centos. I'm sorry, but my current focus is to get it work well with debian. I gonna this after.

And maybe, fixes for debian will fix centos errors (I really hope).

rapiadam commented 9 years ago

+1

jtd1688 commented 9 years ago

+1

SirWaddles commented 9 years ago

xtreamwayz pull request seems to fix this issue, but the executable version on yann's fork seems to be causing other issues on my build?

Sometimes I'm not really certain what circumstances cause it, but if this is the main issue you're experiencing, I reccommend giving that version a go.

This one

yannschepens commented 9 years ago

I do not have my dev. environment currently (client mission). I promise I gonna check this error when I will get back my computer, (2 week).

Please be patient ^^

dkarlovi commented 9 years ago

@yannschepens thanks for the effort in any way. :+1:

LordofFatality commented 9 years ago

Same here - Windows 7 host, CoreOS 738.1.0 guest, Vagrant 1.7.2, vagrant-winnfsd 1.0.11

Thank you, Yann!

LordofFatality commented 9 years ago

Hey Yann, any news? ;-)

Also: Is this related? When executing a single command via SSH on the CoreOS box, CoreOS does not see the shared folders. Instead of

cd /x/y/z

I have to

cd x
ls
cd y
ls
cd z

Do you know a workaround?

If I SSH into the machine for a session I only have to ls the top directory and CoreOS recognizes the subdirectories. But I still have to do it once.

yannschepens commented 9 years ago

Hi Lord, no sorry anything currently, I come back from holidays and I have some work to do.

I think, I gonna work on Winnfsd within 2 or 3 days.

I have to copy issues from Bitbucket to Github too.

Be sure I gonna give you news when I will work on this f*****g problem ^^.

Le lun. 3 août 2015 à 15:15, LordofFatality notifications@github.com a écrit :

Hey Yann, any news? ;-)

Also: Is this related? When executing a single command via SSH on the CoreOS box, CoreOS does not see the shared folders. Instead of

mkdir -p /x/y/z

I have to

mkdir x cd x ls mkdir y cd y ls mkdir z

Do you know a workaround?

If I SSH into the machine for a session I only have to ls the top directory and CoreOS recognizes the subdirectories. But I still have to do it once.

— Reply to this email directly or view it on GitHub https://github.com/winnfsd/vagrant-winnfsd/issues/27#issuecomment-127228138 .

winnfsd / vagrant-winnfsd

Bugs with file creation on host #27