encfs4win - (encfs.cpp:141) error caught in getattr about dokany

[Liryna]

Did you rebuild encfs4win ?
Normally we have not broke compatibility with Dokan 6.0. if you rebuild it should work.

I will not be able to help you much more and It looks like encfs4win is unmaintained.
If you have the possibility to maintained it, it would be great !

[Owyn]

No I didn't rebuild it, And its repository is unavailable now anyway.
I found a github which seems to host it (there is no way to check if it has 100% same files now) - https://github.com/freddy77/encfs4win
but still compiling it is not a thing everyone could do ( http://stackoverflow.com/questions/18993141/howto-compile-encfs4win-on-windows )

[Liryna]

Without rebuild it is for sure that you will have a issue :(
Binary compatibility changed since we have moved to Visual Studio 2013.

Encfs4win seems to be a good projet. If someone want to maintain it, I would be glad to add it to the dokan-dev !

[Owyn]

@Liryna ok... I rebuilt it with VS 2013 and guess what? it gives pretty same error...

23:26:48 (..\encfs\encfs.cpp:141) error caught in getattr

[Liryna]

Ah that's great ! You will be able to debug it now.
It would be nice if you could fork encfs4win with the fix.

[Liryna]

@Owyn Have you been able to make encfs4win work with dokany ?

[Owyn]

@Liryna it worked from the box. just without some feautures which got broken.

[Liryna]

So I will close this issue if you don't mind. I think it is related to encfs4win.
It is pretty sad that even with a good number of users, nobody is willing to maintain it.
I hope someone will take the flag in a near future !

[jetwhiz]

Hi @Liryna -- maybe you have some ideas that can help me fix this issue? I have noticed that when encfs4win is mounted to a drive letter (e.g., "Z:") then everything works well, but when encfs4win is mounted to an empty folder (e.g., "C:\myfiles\mountpoint"), all of the requests for getattr are for the short name (8.3 filename).

For instance, when requesting the file "Z:\file.txt", getattr provides "file.txt". When requesting "C:\myfiles\mountpoint\file.txt", however, getattr provides the file "FILE.TXT".

Normally this is not an issue on Windows, but since we are encrypting the file names in encfs, there is a big difference between "file.txt" and "FILE.TXT". Do you have any ideas as to why Dokan is providing the short filename for mounted drives ("C:\myfiles\mountpoint") but provides the long filename when the filesystem is mounted to a drive letter ("Z:") for us?

[Liryna]

Hi @jetwhiz ,

This is interesting, does C mirror also get FILE.TXT when mounted to C:\myfiles\mountpoint ?

[jetwhiz]

I just did a quick test (dumping Dokan debug output) and it looks like it might be the same on the fuse mirror:

Mounted to "Z:" doing a getattr for "Cygwin.ico"

FileMatch? : .. (Cygwin.ico,0,0)
FileMatch? : bin (Cygwin.ico,0,0)
FileMatch? : Cygwin-Terminal.ico (Cygwin.ico,0,0)
FileMatch? : Cygwin.bat (Cygwin.ico,0,0)
FileMatch? : Cygwin.ico (Cygwin.ico,0,0)
  =>return single entry

Mounted to "C:\dec" doing a getattr for "bunzip2.exe"

FileMatch? : apropos (BUNZIP2.EXE,0,0)
FileMatch? : arch.exe (BUNZIP2.EXE,0,0)
FileMatch? : ash.exe (BUNZIP2.EXE,0,0)
FileMatch? : awk (BUNZIP2.EXE,0,0)
FileMatch? : base32.exe (BUNZIP2.EXE,0,0)
FileMatch? : base64.exe (BUNZIP2.EXE,0,0)
FileMatch? : basename.exe (BUNZIP2.EXE,0,0)
FileMatch? : bash.exe (BUNZIP2.EXE,0,0)
FileMatch? : bashbug (BUNZIP2.EXE,0,0)
FileMatch? : bunzip2.exe (BUNZIP2.EXE,0,0)
  =>return single entry

[Liryna]

I created an issue related to it #293
I am unable to see for now if it is a dokan issue or it is the system that request such names because of the reparse point.

[jetwhiz]

Ok, thank you, @Liryna! I will try to look into the code to see why there might be a difference here.