Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Duplicate folders in /Volumes upon unlocking vault in macOS 10.12 Sierra #464
This is a bug report.
I'm using macOS in version: 10.12.3 Sierra
I'm running Cryptomator in version: 1.2.4 (862)
My vault have the mountname
But after unlock I for some reason end up with two directories as such:
…where the unlocked files are located in
What I've tried so far*:
*When locking the mount it leaves the empty
Any other idea/suggestion on how to troubleshoot and/or resolve this?
Thank you for your bug report!
My impression is that it's a Sierra bug and has nothing to do with Cryptomator per se. I'm able to reproduce the issue with "any" localhost WebDAV server.
Unfortunately, I'm out of ideas on how to troubleshoot/resolve this.
I think that I found a workaround - at least it has been working for me for a few days, macOS 10.12.4 (16E195).
My vault is called Aleph. After unlocking the vault, I do a "lsof | grep Aleph". SInce Aleph is unlocked, it should return an empty output. Instead, it returns the following message:
This stat attempt to /Volumes/Aleph-2 seems to trigger something, because now, after a few seconds, the Finder opens a message saying that the WebDAV server has been unexpectedly disconnected. It gives me the option to ignore this fact or to eject the share. When I eject the share, things work normally again, meaning that on the next unlock, the mount is called /Volume/Aleph again.
For anyone interested in the details: We're using AppleScript to mount the volume, see MacOsXAppleScriptWebDavMounter.java#L53.
Due to the whole refactoring, it's now in webdav-nio-adapter/MacAppleScriptMounter.java#L35, but it's still the same script. Theoretically, we also have a shell script mounter, see webdav-nio-adapter/MacShellScriptMounter.java#L54.
As far as I remember, we have to use AppleScript for OS X >=10.10 because of permission issues. You can't do
Unfortunately, after days of flawless operation, the problem is now re-occurring for me. After turning on the Mac, I started Cryptomater and unlocked the folder. This lead to the (MacOS) error message "Beim Verbinden mit dem Server „localhost“ ist ein Fehler aufgetreten." (roughly "An error has occurred when connecting to server 'localhost'". After that, Cryptomator showed the folder as unlocked, but there were two empty directories in /Volumes, "CryptomatorFolder" and "CryptomatorFolder-1" ("CryptomatorFolder" being the name of the Cryptomator folder).
Locking and unlocking the folder shows the same result, regardless if I delete both /Volumes folders, or if I keep them. Cryptomator, though, shows the respective folder as unlocked. I am able to manually connect to this folder using the Finder menu "Mit Server verbinden..." ("Connect to server..."). This leads to the Cryptomator folder being available as /Volumes/CryptomatorFolder-2.
After that, and after locking the Cryptomator folder and exiting Cryptomator, I cannot rmdir /Volumes/CryptomatorFolder-2 for a while, the error message being "CryptomatorFolder-2: Resource busy". After a minute or so, I can delete the folder, /Volumes now containing no Cryptomator folder at all.
Now comes the interesting part: When I restart Cryptomator and unlock the folder again, this works - but the three folders /Volumes/Cryptomator, /Volumes/Cryptomator-1 and /Volumes/Cryptomator-2 reappear (!), which the former two being empty and /Volumes/Cryptomator-2 being the actual mount point for the Cryptomator folder.
Since it worked so well for a number of days, I take it for granted that, after rebooting, it will continue to work normally for a while, and that this is a very random bug.
As a temporary workaround (tested in macOS 10.12.6): Use Finder to mount your vault. It always mounts the vault in the same directory:
Finder will use the vault’s drive name specified in Cryptomator. You can change this name in Cryptomator by checking “Mount Drive”, then edit the drive name, and uncheck “Mount Drive” again.
If you know how to mount webdav via shell, let me know. Haven’t gotten it to work with mount_webdav.
referenced this issue
Dec 4, 2017
I don't want to be a party pooper, but installed the software on Sierra for the first time (Coming from Boxcryptor Classic)
I've noticed that when mounting the -1 appeared behind the name, so I've immediately went to /Volumes and indeed found two.. Searched the internet and it brought me here..
Anything I can do about it?
Today we released our first beta of 1.4.0, which brings FUSE support to macOS and Linux.
Please retest this issue with FUSE enabled and report your findings in this thread.
If you experience any new issues, please report them and tell us what software version (including macOS version, involved applications, etc) you're using.
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.