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 .
Hi Garrett , feel free to go through https://www.dropboxforum.com/t5/Files-folders/Block-level-sync-for-VeraCrypt-not-working-post-83-4-152-update/m-p/385853/highlight/true#M139160. I am able to use dropbox with the settings and it works fine, but only for *.vc and *.tc files. That is a workaround, stated by dropbox. I am pushing to get a solution for having block level sync (differences only) available for all type of files.
I think it's convenient for someone from Dropbox to share an update on the final pending solution.
John L.2Dropbox Staff
Hi all,
I think there are a couple of issues on this thread.
1. Block level sync should be working for all file types. Please let us know if that is not the case for you. (previous post: https://www.dropboxforum.com/t5/Files-folders/Block-level-sync-for-VeraCrypt-not-working-post-83-4-152-update/m-p/383392/highlight/true#M137525).
2. There is an issue specific to these containers where they can change without the modification timestamp changing. For this issue, you can uncheck "preserve modification timestamps" in the preferences for Veracrypt/Truecrypt. We have also whitelisted files with .tc and .hc extensions to be checked even if the modification timestamps have not changed.
Hope that helps.
Thanks!
--J
John L.2, In both cases, which you have describes (and not only), there is NOT a solution, but workarounds!
@Dropbox
when will the workaround/restriction to .tc /.vc be removed?
so it works again, as it was working up to about September 2019
John L.2 wrote:We have also whitelisted files with .tc and .vc extensions to be checked even if the modification timestamps have not changed.
This does not appear to be working, assuming "to be checked" means checking for any container content changes. Without unchecking the file modification timestamp option in Veracrypt, DB checks for changes and appears to determine there are no changes, even when changes exist.
In my current experience, no indexing occurs unless the timestamp is changed.
John L.2 Thanks for your reply and summing up the issues.
Referencing to your first part of the post (as I personally can't reproduce the second issue): Yes, that is exactly my issue. So block level sync (only the changes are synced = modification of timestamp is on in veracrypt) works fine with the latest version of dropbox. What is not working fine is, that this is restricted only to files with the ending *.vc and *.tc. This is ok as a workaround (suggested as "workaround" by dropbox see https://www.dropboxforum.com/t5/Files-folders/Block-level-sync-for-VeraCrypt-not-working-post-83-4-152-update/m-p/382599/highlight/true#M137114), but we want to have back again the original functionality, where it was possible, to have block-level sync available for ALL filetypes.
Garrett Have you updated to the (latest) version suggested in this thread? Which version are you using? I have 88.4.172 and can't reproduce your issue.
