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

Running on Windows 10 #22

Closed
ajdevries opened this issue Jan 2, 2018 · 3 comments
Closed

Running on Windows 10 #22

ajdevries opened this issue Jan 2, 2018 · 3 comments

Comments

@ajdevries
Copy link

Nice project, good API and happy that it is also available on Windows.

I'm trying to build a FUSE filesystem for OSX and Windows. Got a part working, but when testing on Microsoft Windows [Version 10.0.16299.125] it doesn't work.

Also when testing with memfs.go it doesn't work well on Windows. When running in DEBUG mode I see that all files and directories are uppercase. Some issues that I'm having running memfs:

  • can't create a directory and open it in Explorer;
  • can't change a file contents;
  • see different behaviour when running in CMD and in Explorer.

I'm using the latest WinFSP version.

Can you help me out what is going wrong here?

@ajdevries
Copy link
Author

After some digging. I found the following user errors ;-)

  • I was running the command with a different user is used, and there is some error related to that;
  • when using a mountpoint i.e. c:\u there are issues with capitals.

When not using a mountpoint a z: drive is created and that is working okay.

@billziss-gh
Copy link
Collaborator

billziss-gh commented Jan 3, 2018

File systems on Windows can be mounted as drives or as directories.

Unfortunately file systems mounted as directories must be case-insensitive to function properly. This is because Windows treats file systems mounted as directories as case-insensitive regardless of what the file system reports; it will in many cases lookup files with uppercase names (FILENAME) even if the original application did not do so.

This is an unfortunate limitation of the Windows system and it does not happen when the file system is mounted as a drive or when the file system is case-insensitive.

@ajdevries
Copy link
Author

Thanks for the quick response. Make sense. Will close the issue.

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

No branches or pull requests

2 participants