-
Notifications
You must be signed in to change notification settings - Fork 88
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
Problem with samba share folders (jnr-fuse + winfsp) #129
Comments
Hey, @evial! I think enabling debugging logs might help to understand the issue, you can find an example here (last argument):
|
Thanks @SerCeMan for the tip. Actually, I had already enabled the fuse debug but I didn't find anything relevant. Below the output when opening the file "hot/test/hello.txt" in the shared folder:
The read method is called at the end but no SMB read request is issued by the client (cannot see any in Wireshark) so I think this read is not aimed to return the file content. Anyway, no content data is sent back to the client before it shows the error message. Compared with the debug from a successfull read (from a Linux SMB client), the only difference I noticed is the value of the ShareAccess field in the FILE_OPEN: ShareAccess=7 (fail) vs ShareAccess=3 (success). I have no idea what it means. |
Hi,
We use jnr-fuse on Windows with winfsp for a cloud storage application. Everything works great locally, files can be accessed normally from our mount-point but we're facing a problem when we configure a Samba folder within the mount-point to share the files with other computers. From a Linux SMB client, it works properly but from Windows clients, we have a "directory name is invalid" error when we try to open a file. There's nothing strange in the fuse debug. When opening the file on the client, the open method is called in the FuseStub but for some reasons, the read request is never sent through the SMB protocol. It seems there's something wrong with the open result, maybe winfsp is expecting some information we don't provide with. I know the problem description is vague but do you have any idea what coud cause this issue? Could it be connected with the FuseFileInfo structure? We just set the file handler "fi.fh.set(handler)", nothing more. Any help would be appreciated.
Thanks
The text was updated successfully, but these errors were encountered: