Here is the command I used to display the files in question when the difference was reported: THIS TIME THE FILES WERE IDENTICAL AND HAD THE CORRECT CONTENT! And that is exactly why I wrote the comment on the bug I created. I used commandline recall to execute the diff command a second time on the file in Master and MasterCopy. In this situation I aborted the script which was checking for differences and the sync session. When I checked one of the differences manually I found both the file in MasterCopy and in Master did not have the correct content. Important: I had not written to MasterCopy. In total 20 files were reported to be different between Master and Master Copy. rsync from Master to Vault B in the second sessionĪfter starting the rsync process in the second session I noticed the script session reporting differences for files which had not been altered.the script was in the phase of finding differences between Master and MasterCopy.Now there were two sessions in parallel (as described in my comment above): I manually updated Vault B (rsync from Master to Vault B). and found the expected differences between Master and Vault B. differences between Master and MasterCopy.The script checked for difference in this order:
Before I update vaults B, C or D or the directory MasterCopy, I check what the differences are (automated through a script). There is a directoy on a second disk which holds a copy of the unencrypted Master vault. I do not have insight in how FUSE works, but had not expected some confusion on the Cryptomator/FUSE side could deliver the wrong content for a file outside any Cryptomator directory/mount maybe my description was not clear enough. After reopening the Master vault all 20 differences were gone. Of course it did not really change the content but I had been given the wrong content before. How strange is that? Closing and reopening the Master vault changed content of a file outside of a FUSE mount point or a Cryptomator vault. _NOW THE DIFFERENCE WAS GONE!_ The files had the expected content. So I closed the Master Vault and reopened it. I expected screen snapshots from technical documentation, What I got looked like to be two scenes from an animated GIF.
They happened to be image files so I opened both of them. I picked one of the files that were reported to be different and checked from the command line with diff. Session 1 was reporting 20 files to be different. _VaultB_ is the FUSE mount point of VaultB The directory holds an unencrypted copy of the Master _CopyofMaster_ is a directory on another diek (APFS encrypted), but NO CRYPTOMATOR VAULT. _Master_ is the FUSE mount point of the unencrypted Master vault
Now the file vmail_edited.wav had the expected content. Instead of copying the file vmail_edited.wav from B or C to A, I closed vault A and reopened it. The file vmail_edited.wav in B and C contained the expected audio file. Upon further investigation it turned out the file vmail_edited.wav in the top level directory of A had the content of the file AnkeTasmanien.JPG, also in the top level directory of A. One file which I had not touched/altered in years was different between A and B, A and C. Before syncing, I check which files differ. I always only change files in A, then from time to time sync the content of A with B and C.
A: Cryptomator FUSE mounted unencrypted directory.I regularly sync the unencrypted content from one vault with other Cryptomator vaults and one unencrypted local directory.Operating system and version: macOS Catalina Version 10.15.5 Beta (19F62f).One file in the FUSE mounted unencrypted file system had its correct name but the content of another file in the same directory.