You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
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 .
Julia20
Dropbox Staff
Dropbox StaffHi everyone.
Follow-up on my post above. We allow using ".tc" and ".hc" extensions as a work around. In the meanwhile we are looking into a better long term solution.
Thank you for your patience!
Julia
Hello Julia20 , I have tested it and it looks like it the workaround is working.
For all users, who have the same problem: Requirements for the workaround for windows:
- Updated to the current dropbox version (in my case: 87.4.138 )
- Veracrypt with option activated: "Preserve modification timestamp of file containers"
- Renaming of the verycrypt container file to *.tc.
- Mounting, changing of a file, umounting the containers. A change in a 8gb fiel took about 30sec to sync all changes, which indicates, that block-level sync is working in this corner case
To be honest, I am still not satisfied. I would like to see an offical statement of Dropbox here. How can something critical even happen? I am not sure if you really have unterstood the consequences of this failure. A loft of people have lost data, as people thought block-level sync was working, but it was not. Please be so nice to answer my questions:
- How can it be, that there is no official statement (example an e-mail with an apology for heaving led to data loss) with a description, what happened here? This would be the bare minimum!
- How long will it take, until it is possible to have block-level sync for all files available again? Please provide a timeframe.
- What will Dropbox do in the future, to avoid such a huge mistake? You really need a better QA.
- When will there be a changelog for new releases?
Thanks in advance for your qualified response.
