-
Notifications
You must be signed in to change notification settings - Fork 82
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
Not able to mount Fuse Drive on a Mapped Network Drive in Windows #33
Comments
Can you please post the full FUSE command line that you use to mount the file system (i.e. the arguments to Keep in mind you cannot mount a "network" file system to a directory. Only "disk" file systems can be mounted on directories. |
Sure, here it is: options := []string{"-o", "volname=Altair", "-o", "uid=-1", "-o", "gid=-1"} Note: The directory "Fuse" do not exist on R: |
In order to mount on a directory, WinFsp must be able to set a "reparse point" on the (newly created) directory. This is done in the WinFsp internal call Is the network drive on a Windows server? For example, I believe there are some issues with reparse points on Samba shares. |
Sorry for delayed response. The Network Server Setup is on Linux (OneFS). |
If the server properly supports reparse points (e.g. a Windows server) I believe that it should work. |
I have a mapped network drive (R:) which is pointing one of the folder on the network E.g. "\server-share\files". When I try to mount FUSE drive to let's say "R:\Fuse" I get below error "Cannot set WinFsp-FUSE file system mount point".
However, I am able to mount Fuse to Local Drive like "C:\Fuse". I have ensured "Fuse" folder is not present.
Any idea on this issue?
The text was updated successfully, but these errors were encountered: