sshfs-win stops working, randomly, requires restart of winFSB service to fix

[h3lo]

Been using sshfs-win for a little over a month now. I've run into an issue where the mount will randomly die.

I have been able to reproduce the issue multiple times tonight, but am not sure how to troubleshoot further. Should the bug for this be on the winFSB project?

I mounted the sshfs filesystem, and then played a video from the mount via VLC. It plays fine for an hour - 2 hours. Randomly, the video will freeze (VLC handles it gracefully). The network location became unavailable. I am not able to disconnect (produces error). I also am no longer able to mount the same or any new sshfs mounts. Restarting the winfsb service gets everything back to a state where I am able to disconnect and reconnect (but the issue comes back an hour or two later).

Before restarting winFSB, I tried using the cmd prompt but it had not effect:

Microsoft Windows [Version 10.0.18363.900]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Users\asdf>net use
New connections will not be remembered.

Status       Local     Remote                    Network

-------------------------------------------------------------------------------
             Z:        \\sshfs.r\asdf@host!22\mnt
                                                WinFsp.Np
The command completed successfully.

C:\Users\asdf>net use Z: /delete
Z: was deleted successfully.

C:\Users\asdf>net use
New connections will not be remembered.

Status       Local     Remote                    Network

-------------------------------------------------------------------------------
             Z:        \\sshfs.r\asdf@host!22\mnt
                                                WinFsp.Np
The command completed successfully.

C:\Users\asdf>

Says success but did literally nothing.

[resettarget]

I'm having same (or only similar?) issue.

sshfs and winfsp both are latest version (as of July 17). Worked for a while then broken. I could disconnect but when tried to redo map network drive, it failed. After relaunched winfsp.launcher service (via Windows Task Manager), could map drive successfully again. Will keep monitoring how long this can last.

My environment: Windows 10 Version 2004 sshfs: 3.5.20024 (from Windows Control Panel Programs and Features) winfsp: 2020.1 1.7.20172 (from Windows Control Panel Programs and Features)

the other side is Ubuntu 18.04.4 LTS in a VM, running in VMware

My Windows (sshfs and winfsp) and VMware are actually on a same PC. My regular Putty SSH from Windows to the Ubuntu VM has been pretty stable and I haven't notice anything strange.

[willyd]

Same issue here. Windows 10 connecting to a Ubuntu 18.04 machine.

Thanks to @h3lo for the workaround, restarting the service solves the problem temporarily.

[The-SamminAter]

Same issue here, Windows 10 connecting to an iPhone.

I'll try using the workaround now.

[giampaolo44]

Same problem, killing the Window File System Protocol from the task manager did not solve it so far. Frustrating.

[CarbonMac]

Running into this as well, restarting the WinFSP.launcher service works, but something is wrong in the chain. I am willing to help contribute but need to know what is needed.

Explorer.exe complains about insufficient system resources so I am wondering if it is overstepping some imposed resource limit

An easy "hotfix" for this for users would be to setup task scheduler to restart the service every X hours or at a certain time

[darkuranium]

Possibly related to #59? (in particular, see https://github.com/winfsp/sshfs-win/issues/59#issuecomment-950024206)

[ghost]

don't quote, answer pls

[muhammadsameer3003]

It did work @CarbonMac . Thanks!