Intensive I/O causes resource unavailable

Open
#59 40 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
ubuntu
Domain
networking, operating-systems

Research direction

Start by reproducing the mapped-drive failure with the listed Ubuntu, Windows, SSHFS-Win, and WinFSP versions, then inspect the Windows events showing the sshfs service restart loop. Done means identifying why intensive I/O causes the resource to disappear and preventing the access-denied failure or documenting a confirmed workaround.

Written by the indexing model from the issue text.

Description

My setup:

  • Ubuntu 18.04.1 LTS in Hyper-V,
  • Windows 10 1803 17134.1,
  • SSHFS: sshfs-win-2.7.17334-x64.msi,
  • WinFSP: winfsp-1.3.18160.msi.

I establish a connection to the resource using the official way via „map network drive”. Connection is done via host-only interface (not the NAT one). On the Ubuntu I've created some Symfony projects and want to use this on host's PHPStorm instance. Starting and indexing works perfect until — via some reason — the mapped drive's contents completely disappears with a message „access denied” under Explorer.

I've tried to investigate this issue a bit and found out that tweaking sshd params has no affect on this. In Windows events log for WinFSP there's many entries like:

sshfs: The service sshfs has been stopped.
launcher-x64: terminated sshfs\asfsdf@192.168.xx.yy\..\..\workspace
launcher-x64: create sshfs\asfsdf@192.168.xx.yy\..\..\workspace
sshfs: The service sshfs has been started.

and these appear like within the loop.

I'm pretty fresh to WinFSP (and amazed by iops it does) so if is there any additional debug information needed, point what to do, please.

Dominant language
C
Stars
6.4k
Forks
315
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from winfsp/sshfs-win

All issues in winfsp/sshfs-win

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.