search

jetwhiz / encfs4win

Windows port of EncFS
https://encfs.win
Other
400 stars 41 forks source link

Error 1450: Insufficient system resources exist to complete the requested service #91

Closed elieux closed 5 years ago

elieux commented 6 years ago

Environment

Description

Directory listing is interrupted if it takes too long.

Steps to reproduce problem

  1. Mount an encrypted directory.
  2. On the mounted drive, open a (sub)directory with lots of entries.

Expected behavior vs. actual behavior

Expected: Takes some time, then finishes successfully.

Actual: Takes a fixed amount of time, then fails with the error 1450.

Relevant logs

AFAIK this has been the case ever since the original encfs4win (I have been using that one until recently). From what I remember about my research then, there's a timer in Dokan that will kill the callback and produce this error unless the callback postpones the deadline regularly.

A 1000 entries seems to reliably reproduce the issue on my machine. It doesn't even have to be a long directory listing, just reading from a network (or otherwise slow) drive can make the listing slow enough.

elieux commented 6 years ago

It is also dependent on the filesystem cache. After listing my 1000-entry encrypted directory once, the mounted one starts working just fine.

jetwhiz commented 6 years ago

Hi @elieux -- thanks for the bug report!

This sounds like it might be related to the general stability issue that was reported (https://github.com/jetwhiz/encfs4win/issues/62), which may be due to the fact that Dokany thinks encfs4win has crashed while it is reading/opening files that take a while (as you mention). Unfortunately I don't believe access to increase the timeout is available through the FUSE interface. The closest we can get is by setting the daemon_timeout parameter.

Can you try using "-o daemon_timeout=M" (where M is in milliseconds) on your mount and see if this helps the issue at all?

Otherwise the Dokany 2.0 beta version (https://github.com/dokan-dev/dokany/releases/tag/v2.0.0-BETA1) will hopefully address this issue better.

jetwhiz commented 5 years ago

Hi @elieux

Have you been able to confirm that this issue still exists with the latest versions of encfs4win and Dokany? There have been a lot of stability updates in Dokany that may have helped this issue.

stale[bot] commented 5 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.