Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Solved
Block-level sync for VeraCrypt not working post 83.4.152 update
Greetings all,
After DB auto-updated to 83.4.152, I noticed that the block-level syncing doesn't seem to be detecting changes anymore for my VeraCrypt container.
Before the update, everytime I di...
Hi all, we've brought this to our team and wanted to follow up.
While we've presented a workaround: either by turning off the "preserve file modification timestamps" setting in the application or naming the file with a ".tc" or ".hc" extension, we want to be transparent about our current priorities and unfortunately, this means that we won't be able to delve deeply into this in the near future.
We're still tracking these reports, and will make sure to inform you right away of any changes.
Thanks for understanding .
This was NOT solved! All that does is cause Dropbox to sync the entire encrypted volume. It STILL is NOT doing a block-level sync.
asimpson417 wrote:This was NOT solved! All that does is cause Dropbox to sync the entire encrypted volume. It STILL is NOT doing a block-level sync.
Hi asimpson417,
I wanted to double check my test, since your reply gave me a bit of doubt. Thus, I did the following couple of tests:
1. I opened up my VeraCrypt encrypted container, which is 4 GB, added a small text file, and dismounted (without preserving the container's timestamp, as mentioned). DB did detect the delta and synced the container within ~20 sec. I verified on another machine and the container did sync with the added text file after I remounted.
2. I repeated the test by remounting the *.hc file after the sync completed, deleted the text file, modified an Excel file, and dismounted the container. DB again detected the delta and synced the container in approximately the same duration (~20 sec).
Given that my upload speed is about 5 Mbps, my conclusion is that some form of block-level syncing is happening, as it would take it much longer to re-upload an entire 4 GB encrypted file. Actually, I did compare the sync time to when I was conducting the workaround of renaming the *.hc file, and the sync is significantly faster.
I will concede and say that I remember the previous versions being relatively faster after I dismounted the *.hc file when editing small increments of data, but unfortunately, this is subjective as I did not time the sync duration before the current version.
Please let me know if you're seeing different results. Thanks.
I had done a similar test, but with TrueCrypt ending in .tc extension. The entire encrypted volume was only 300MB, but took over an hour to upload (our DSL upload speed is less than 1Mbps, even though download is much faster). The normal sync would have been done 5 or 10 minutes maximum.
Perhaps others should do some tests with VeraCrypt to get a general consensus, and possibly also test with TrueCrypt to see if the fix only works with VeraCrypt. (Or if others see the same problem I saw).
