sshfs-win
sshfs-win copied to clipboard
winfsp
can not disconnect
It took a while but I got sshfs-win connecting to my desktop from my laptop. It's looking great, and super useful.
However, for some reason firstly the drive names are strange.
I expected the drive names to be C: or just C, but this is my drive listing:
Not sure what that dot character is.
Secondly for some reason, right-clicking on the mapped drive and hitting disconnect gives me a windows dialog with the following message:
This network connection does not exist.
I looked around and some people mention Dokany, but I have never heard of that, so I assume it's not installed. I also saw I should make sure WinFsp is at the top of my network provider list so I followed a tutorial, it was already at the top.
Lastly I went onto my remote machine, and deleted a folder from there, but when I list that same folder through the sshfs mapped drive, the folder still exists there. I tried F5, Ctrl+R, leaving the folder, and opening it back up.
Not sure what else to do to diagnose this... Would appreciate any assistance.
Ignore the part about the view being stale and not refreshing. The folder delete had failed (I guess the file was in use or something).
The rest of it is still an issue though.
How are you using SSHFS-Win exactly?
It looks like you are mounting the file systems as directories rather than drives.
@billziss-gh I'm not sure what gives you that impression.. My remote machine is mapped as drive X: for me through SSHFS-win, and I got it by following the instructions in the main readme at: https://github.com/billziss-gh/sshfs-win
But I did some trial and error with the connection string, because I wanted to host the root of my computer, so it shows the drives. I believe I ended up with a connection string like: \\sshfs\192.x.x.x\/
I can double-check if that looks wrong to you, but I got that through some hints in some other ~tasks~ Github issues. I doubt it matters but I also kept trying to get sshfs.k to work, but I failed miserably to do that through the explorer UI wizard.
What I found surprising is that you have directories C·, D·, E·. These look suspiciously like the drives C:, D:, E:, with the colon (:) converted to a Unicode character in the Private Use Area. (This is something SSHFS-Win/WinFsp does because the colon (:) is not a valid filename character on Windows.)
Hence my previous question/comment.
To mount the root directory use \\sshfs.r\USER@HOST syntax.
Interesting. I'll try to use the .r suffix to mount the root instead tomorrow.
I just thought of something that might affect things.
My desktop's locale is Japanese, which results in things like path separators looking weird in some programs. Here's a typical CMD window on my desktop:
Could this affect things?
Connecting through WinSCP, I have no issues.
Same issue met. Map "\sshfs\[email protected]" to driver Z: . The mapping works and all files can be accessed normally. (And very fast. Greate work!) But when I try to disconnect driver Z, I get this message: "此网络连接不存在。"(means: This network connection does not exist.)
OS: Windows 10 Pro 1903
Package Installed: winfsp-1.6.20027.msi sshfs-win-3.5.20024-x64.msi
@roa-nyx this may well have to do something with the path separator character. I recall there is an open issue in WinFsp about this.
@billziss-gh Interesting. I just had a look through open issues for path separator but couldn't find anything. Do you recall which issue this might be a duplicate of?
The issue is actually in sshfs-win. See #126.
I am going to make this into a WinFsp issue to make sure I look into it.
EDIT: I have transferred the mentioned issue to billziss-gh/winfsp#302
I'm also encountering the "this network connection does not exist"-issue when trying to unmount an sshfs mount. I don't have any non-standard backslash or anything, so that can't be the issue, and my mounts have normal colons.
However, for me this issue only happens for failed network mounts. That is: If I successfully mounted a network drive, i.e. \sshfs.k\user@host\valid_path, then I can also successfully unmount it. But if mounting failed due to an invalid path (I've had problems both with symlinks and with absolute paths (except for the root directory)), then the file system still appears to get mounted, but doesn't work and can't be unmounted, giving that "this newtork connection does not exist" error message.
So at least for me the issue seems to be that the network drive is left in some invalid state when the mount fails due to an invalid path.
I have the same problem as @amaurea : I got disconnected, and now I can't disconnect that drive
