We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
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 dismount my VC encrypted container, DB will index the file and compare the deltas at the block-level -- syncing the block-level changes. However, after the 152 update, I've noticed that even with lots of changes in the VC container, after I dismount, DB detects no changes to the encrypted file. I end up having a bunch of conflicts when trying to sync between machines via the "rename the file and rename it back" approach.
Could someone share resolution or your similar experiences if you're also using encrypted containers with DB?
Thanks,
BPH
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 .
I'm seeing the same thing. It also stopped doing block-level syncs for TrueCrypt encrypted files (.tc extension). I've been using Dropbox for years with both TrueCrypt and VeraCrypt files and this new version 83.4.152 is the first update to break the detection of block-level changes when the encrypted volume is dismounted.
Please fix ASAP!!
PS: The only workaround I've found is to use: Copy filename.hc +,,
which forces a date modifed update on the file, but then Dropbox must upload the entire file (not just modified blocks) so it's terribly inefficient (not to mention inconvienient) . If they don't fix soon, I'll have to switch to a different cloud storage provider.I have the same issue, but I think it started with version 82.
The ugly "workaround" I use, is to copy the "file" daily to "file_yyyymmdd", this syncs, and the immediately delete the file. While the orginal file is not synced, doing this I have a daily history, I can get if needed.I think drobox either wants to save resources or has introduced a bug, it seems that a file is no longer checked on close alone, but only on close and the file date has changed. (I use the mode to not change the timestampo of the file)
- HI all,
Actual reason is Dropbox FS restrictions set: https://help.dropbox.com/installs-integrations/desktop/system-requirements#desktop Take a look especially on FS restrictions for different supported platforms.
Hope this casts some light.
I am having the same problem. I have a Truecrypt and over it has stopped syncing and the date doesnt change on the encrypted folder and online the version history doesnt record any new version unless I change the name of the file.
I will probably wait a couple of weeks but if not fixed change to another provider
GH
I am also having the same problem. I've been using Truecrypt and Dropbox for years (and only on 1 PC), and Dropbox used to upload my changes automatically when I dismounted the Truecrypt volume at the end of a day's work.
But, for the last few days, it has either failed to recognise that there have been any changes, or, if it does recognise changes, it renames the up-to-date version on my hard drive as a conflicted version, then starts to download the old version to my hard drive, whilst uploading the "conflicted" version. And as both files are quite large, this takes several hours, and the upload speed slows right down to somewhere between 1 KB/sec and 100 KB/sec.
Hello people,
I am using Veracrypt on my files that are also shared with Dropbox. I have used Veracrypt for almost half an year and everything was absolutely fine until 1 month ago when Dropbox is not synchronising the files.
I tried everything described in the help section, but it did not resolve my problem.
I unliked computer 1, then linked it again. Checked the uploaded files from the Dropbox web and they were the newest version. I unlinked my Dropbox account from my Computer 2, deleted all files from my Dropbox folder, linked again to my account and even then the files that it dowloaded were the old ones. I don't even know how the old one are comming from.
Does anyone knows what could be the problem?
- Walter
Dropbox Staff
Hello there JhonyWalker - thanks for the report!
As your inquiry echoes the OP's description and some similar reports we had from other users, I moved your post under this thread to keep things neat around our Community.
As John L.2 mentioned above, our team is looking into this matter while we speak while, in the meantime, you can try disabling the "Preserve modification timestamp" in VeraCrypt and/or TrueCrypt's preferences or (quoting John here) "touching" the files to force them to sync up.
(https://superuser.com/questions/10426/windows-equivalent-of-the-linux-command-touch/764721#764721)
Thanks for your patience while we look into this matter and let us know if you come up with any additional questions.
Hey Guys,
for those who have still problems. If your changes to a file or a container are done, just try to pause the sync in dropbox. Wait some seconds and then resume.
If I do so, dropbox recognises a change and is syncing. And it is using block level sync.
Just a work around. I will try to automate this for my needs.
Maybe it helps.
Greetings
FatCharlie
Solution is very simple. Go to settings in truecrypt/ veracrypt , in preferences window, uncheck preserve modification timestamp of file container. so that file will note modification date and time and sync in dropbox.
santhosh1000 Your reply indicates, that you didn't go through the whole thread. Please do so and feel free to edit your comment.
santhosh1000 escribió:Solution is very simple. Go to settings in truecrypt/ veracrypt , in preferences window, uncheck preserve modification timestamp of file container. so that file will note modification date and time and sync in dropbox
I agree When synchronization begins Dropbox calculates the time it will take. In principle it informs hours, but quickly synchronizes within 15 seconds at the latest 2 GB and obviously only synchronizes the differences. Same behavior in three different notebooks and I have verified that the synchronization is correct. It was a surprise to find this result.
I agree that Dropbox should find a definitive solution, without having to modify third-party SW settings. Simply my comment points to the fact that the workaround works.santhosh1000 Still not sure you got the point. Again: Removing the option in veracrypt is not an option. I have an 8gb file, that take of course takes WAY LONGER to sync than it would, if it would only sync the differences. Removing the option in veracrypt is not more than a workaround, but not an acceptable solution.
