Closed ldexterldesign closed 4 years ago
Strangely, ditto
(basically macOS version of cp
) says these .mp4
files don't exist, all other ~4000 files transferred successfully:
... so I suspect cryptomator (and/or Dropbox, where the vault was stored) has mangled these files 😕
Huff, poor macOS Finder search performance, unsure if this is connected but I'd consider it normal?:
FYI the original goal of transferring the contents of my vault to a new one was to see if performance would be better (inc. macOS enabling Spotlight, but I now presume this is a separate issue)
FYI the ~3 files which didn't transfer here transferred OK on their own (i.e. one by one)
ldexterldesign@Lewiss-MacBook-Pro ~ % ls -l /Volumes/_cryptomator/gtd/home/calendar/Sanitise\ device\ -\ apple/serif/affinity
total 3487972
-rwx------@ 1 ldexterldesign staff 599132806 21 Feb 09:26 designer - 1.8.0.5 - tnt.dmg
-rwx------@ 1 ldexterldesign staff 247 21 Feb 10:11 mac-torrents.io.webloc
-rwx------@ 1 ldexterldesign staff 588954246 21 Feb 09:26 photo - 1.8.0.166 - tnt.dmg
-rwx------@ 1 ldexterldesign staff 597752454 21 Feb 09:26 publisher - 1.8.0.556 - tnt.dmg
The designer*
and photo*
files here won't transfer by any means (inc. cp
, ditto
). I compressed (i.e. native macOS zip) them and transferred the Archive.zip
successfully but get this error when attempting to uncompress Archive.zip
:
... so I think it's safe to say between cryptomator and/or Dropbox these files got corrupted which doesn't leave me feeling confident about using cryptomator and/or Dropbox again 😟
Why the hell does it claim 32768 < 0
?
I think what the buffer meant to say is: 32768 >= 32768
. The position inside a chunk must be within [0; 32768[
. @cryptomator/libraries we should check our arithmetic.
Problem seems to lie in this piece of code that can be invoked simultaneously by multiple threads:
The problem with this is, that the limit/position of the same non-threadsafe instance gets modified. Instead every thread should use its own markers.
Side note: Same applies to writing in theory, however this error never occurred due to exclusive write locks in other places (fuse-nio-adapter, dokany-nio-adapter).
Hi @overheadhunter,
Thanks for reply
Do you know the cause of my issue and whether it will happen again?
Sincerely
Do you know the cause of my issue
Yes, see previous comment. We think we fixed it and scheduled the fix for the next release.
whether it will happen again
With the current version, it might happen again, if multiple threads read from the same file simultaneously. This is completely recoverable and your data is unharmed, since this bug can not happen during write (due to exclusive locking).
That said, as a temporary workaround you can switch on single-threaded mode by adding -s
to the FUSE mount options in your vault options dialog.
Hi all,
Thanks for saving my privacy!
Hope you're well
As title
I'm trying to transfer the contents of my vault to
a new vault (didn't work so now trying something simpler)my desktop (same issue) but getting the following error when transferring (e.g. moving / copy/pasting):Surprisingly not much info' to troubleshoot this error online
I've inspected the files for permissions and/or extended attributes but nothing sticks out. The only pattern I see is that it appears to be larger single files (e.g. >100mb, mainly video) and these flat out won't transfer in macOS so I have to resort to using shell (i.e.
cp
command).I'm left having to prune transfer files every time the bulk transfer aborts which is very time consuming
Log
☝️ Again, notice here it's a
.mp4
(i.e. video file)Screen shot:
Anyone have any clue what's going on here or any possible workaround?
If you're reading and:
Welcome feedback/input
If you have any issues (e.g. questions/queries) then happy to help
Keep up great work!
Hope this helps & to hear back
Sincerely
hardware: Apple, MacBook Pro (16-inch, 2019) software - operating system: Apple, macOS, 10.15.4 (19E287) software - application: cryptomator, 1.5.5 (dmg-2260.108)