d:\VAULT1 is my root vault directory. I would like to mount it on d:\DATA1, an empty directory not currently in use by any process (just created). I go to the options and set the mounting point then unlock. There is no error reported but the directory d:\DATA1 is empty.
For this vault, activated the “Custom mount options” with the line: " --options CURRENT_SESSION,STD_ERR_OUTPUT --thread-count 5 --timeout 10000 --allocation-unit-size 4096 --sector-size 4096"
Activated “Debug logging”
Created in my home folder a file called “StartCryptomatorWithDokanDebug.cmd” and pasted the following into the file: "“C:\Program Files\Cryptomator\Cryptomator.exe” 2>“C:\Users\admin\dokan.log” 1>“C:\Users\admin\cryptomator.log”
Unloked my vault (VAULT1)
On revealing the folder “j:\DATA1” is empty (this is the error).
In Windows event viewer > Windows logs > System, I get 36 information events at 20:27:35 for dokan1 - but I cannot upload the file here because I get the message “Sorry, new users can not upload attachments.” So let me know if you want me to pass it to you by other means.
I would greatly appreciate some help on the problem raised.
I would also like to know: has anyone successfully mounted a vault on the same file system, for instance mounting d:\VAULT1 on d:\DATA1? Or do you have the same problem (vault mounted but empty)? So I would know if this is a problem with the product itself or rather with my configuration.
I tried to reproduce that but couldn’t.
Works like a charm on my system. Vault is not empty
OS: Windows 10 Pro 20H2
Ok. It turns out that Windows Explorer creates a conflict. I noticed that when I close all my Win. Ex. windows, everything works fine. I can mount the drive and reveal the files in it. But if I am currently having a Win. Ex. window open, it does not work most of the time.
So I tried to refine the diagnostic to determine exactly when it fails, having a Win. Ex. window open.
Remember, my vault is in J:\VAULT1. It turns out that:
If I open Windows Explorer and just select the J: drive on the left pane, the mounting works fine.
Now if I just expand the content of the J: drive on the left pane, it stops to work. No need to even explore the content of the J:\VAULT1 folder to make the mounting fail.
Same result (failure) if I now collapse the J: drive in the left pane and go to another drive letter. At this point one needs to close Windows Explorer to make things work again.
So now I guess I have a workaround, but the question still remains: is that an expected behavior?
Can someone reproduce the same pattern or is it again something to do with my configuration?
The problem you are experiencing might be related to the following issue on our bugtracker:
Maybe some application (explorer, plugin, anything), opens provisionally a handle to the mount directory, which locks the directory and prevents the Dokany driver from transforming the directory into a reparse point.
Thanks Michael, Infeo for the input. Indeed the open handles are the cause.
I have just tested with the sysinternals/handle tool and I could verify that as soon as I expand my J: drive in Windows Explorer, Windows opens not 1 but 2 handles for each subdirectory therein. Then, I only need to close the two handles opened on the mounting point for things to work again.
I don’t know why my Windows Explorer behaves this way on my system. Maybe it’s some other product I’ve installed, but I can’t be sure.
Anyway, this thread can be closed as far as I am concerned.