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 .
Hello Jane ,
thanks for your reply. I have created ticket #9882384. Just to get you a feeling how much people are affected, I will show you just some examples: Please check the description of asimpson417 : https://www.dropboxforum.com/t5/Files-folders/Block-level-sync-for-VeraCrypt-not-working-post-83-4-152-update/m-p/376542/highlight/true#M133850. Feel free to have a look at that too:https://www.dropboxforum.com/t5/Desktop-client-builds/Stable-Build-84-4-170/m-p/375569/highlight/true#M5569 and https://www.dropboxforum.com/t5/Desktop-client-builds/Stable-Build-83-4-152/m-p/372885#M5539
I have tested and reprocuded the issue on a daily basis with latest dropbox builds. It is not just one file but any tested file. The issue is about Veracrypt (VC) /Truecrypt (TC) container files in combination with Dropbox. The relevant part is the option "Preserve modification timestamp of file container" within VC, which offers the option to only sync parts of the file and not the whole file.
Current situation:
A VC container file (8 gb) is located in the Dropbox. This file is mounted with VC. Some changes are done within this file. After that, the file gets unmounted and then all 8gb have to be synched again via dropbox. This causes very long waiting times if the files are big(ger) like in my case.
Previous situation:
A VC container file (8 gb) is located in the Dropbox. This file is mounted with VC. Some changes are done within this file. After that, the file gets unmounted and and only the small changes, that have been done within the file, will be synched via dropbox. (referenced as "Block-Level Sync" in the topic)
I personally have not been able to find a working dropbox version but according to nei a. , some 81 version should do the trick. Still, it would just be a workaround and we are looking for a stable solution.
Please push this on your end as a lot of people are affected and not happy with this behaviour. Please also clarify is this is expected behaviour or a bug. Timeframe for the the occurence of the issue should be somthing around beginning till mid of october.
9912915
first I have been asked ot make a screenshot, I do no really know how do this for something that is not working.
Then I got the answer:
"The problem you’re experiencing appears to be caused by another app or service you’re using, not by Dropbox. We’re unable to provide support for third-party apps or services."
Which is funny, considering this worked since 2010, the other truecrpyt did not change, only the dropbox app. .....
Now,I just asked them to temporarily disable auto updates so I can properly test/install earlier versions. Lets see if they will do this.
Would like to report that I am experiencing the same issue. I am a VeraCrypt user.
Ticket #9924951
This is not a problem with third party programs. This is a Dropbox programming failure. It’s simply a case of Dropbox no longer correctly identifying changed blocks in TrueCrypt and VeraCrypt volumes when they are dismounted. So, they are not syncing the changed blocks. Now a programmer must have programmed that in at some point in the past – but the new "improved" Dropbox client does not have that capability programmed in. In other words, the new programmers are playing catchup to figure out what was already working in the older versions of Dropbox. They need to look carefully at how the old Dropbox client identified the changed blocks on *.tc and *.hc files when TrueCrypt or VersaCrypt dismounted the encrypted volume file. It appears to detect the dismount, but is not actually syncing the changed blocks.
Dropbox is not interested in finding the cause of this or getting a solution.
This is what I got for my request to pause/halt autoupdates temporarily for my account (they used to do this, so I know they can do it):
"Regarding the update, I understand this can be frustrating to you, however, we are unable to disable the auto-update for the Dropbox Desktop Application, please keep checking back with us to see if there is any change regarding the behavior of this specific file. "
I am out now.
John L.2Dropbox Staff
Hi everyone,
Thanks for the reports. Our engineering team is looking into these issues.
As a temporary work around, can you try disabling the "preserve modification timestamp" in preferences for VeraCrypt or TrueCrypt?
Another thing to try would be to 'touch' the files to try and get them to sync up (https://superuser.com/questions/10426/windows-equivalent-of-the-linux-command-touch/764721#764721).
Thanks,
J
