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
How to debug "Cannot create WinFsp-FUSE file system." #229
Comments
A couple of questions:
BTW, you do not need the .NET framework for WinFsp unless you have a .NET file system. |
That's the full message. (next line contains sshfs failed)
Ok! |
I am looking at the code here and the only reason that you would get the message without an additional explanation is if you run out of memory (which of course sounds weird). Do you have Visual Studio or other debugger on the machine that is failing? If yes, I could give you some pointers on how to debug this with SSHFS. |
It shouldn't be running out of RAM during this test. Almost nothing else running. |
Yes, the memory problem sounds very unlikely, especially because the amounts of memory allocated are miniscule. I suspect that I am misdiagnosing the actual reason, perhaps only debugging the code on your machine would give us the real answer. |
Re-thinking this a little. |
I doubt that it is the anti-virus because there are no file system interactions if no explanatory message is printed. Basically the code allocates some memory and if that fails it prints the message you saw. Once it calls |
SiriKali backends produce that error when winfsp is not installed. Can the OP confirm that winfsp is installed in the affected computer. |
I have a
working ok on two windows 7 pro machines.
However when running the same command on another machine, adding "-d", I get a
Cannot create WinFsp-FUSE file system.
-error. And the sshfs service fails to start.
I tried installing the newest .NET framework, but had no effect on the situation. This is a Win7 home premium install.
Any ideas on how to figure out what is causing winfsp to fail?
The text was updated successfully, but these errors were encountered: