Skip to content
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

Lxss folder does not update FS properly #1141

Closed
kjhoerr opened this issue Sep 30, 2016 · 3 comments
Closed

Lxss folder does not update FS properly #1141

kjhoerr opened this issue Sep 30, 2016 · 3 comments

Comments

@kjhoerr
Copy link

kjhoerr commented Sep 30, 2016

I discovered this when trying to use Git with BOW and accessing the repository from IntelliJ, as a Windows application. Modifying files from Windows using C:\Users{user}\AppData\Local\lxss\ is buggy:

syncdbashpwsh2

As you can see, saving b.txt in Windows doesn't even make it appear on the Bash side. If I try to write to that filename from Bash, all it gives is an I/O error.

Using /mnt/c/ in Bash rather than using C:\Users{user}\AppData\Local\lxss\ in Windows seems to actually work. There's an issue with Powershell using direct I/O (modifying a.txt and c.txt in the example), but that's a different bug entirely, as it still exists in /mnt/c, and Command Prompt does not have the same issue..

Microsoft Windows [Version 10.0.14393]

To reproduce:

  1. write a file to a path on 'C:\Users{user}\AppData\Local\lxss':
    PS C:\Users\{user}\AppData\Local\lxss\home\{user}> echo "Hello, World!" > file.txt
  2. Open BOW to the same location and attempt to write to the same location:
    {user}@{hostname}:~$ echo "hello" > file.txt
  3. BOW will produce the following error:
    -bash: file.txt: Input/output error

strace gives no extra information.

I remedied my own issue by using Git in the /mnt/c/ directory instead.

@fpqc
Copy link

fpqc commented Sep 30, 2016

Known issue, by design. Do not enter %localappdata%\lxss unless you know what you are doing.
It was hidden for a reason.
Touching anything with the wrong tools will break it.

Things you can do safely: Read/move/rename files
Things you cannot do safely: Create/edit/copy files

And never do anything while bash is running.

@kjhoerr
Copy link
Author

kjhoerr commented Sep 30, 2016

Okay. I didn't consider using /mnt/c/ whatever reason, and ~lxss was the only other solution that I could find online. All things considered, it's a non-issue.

Thank you! You can close this if you want.

@fpqc
Copy link

fpqc commented Sep 30, 2016

You can close it too!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants