Need to see if your shared folder is taking up space on your dropbox 👨‍💻? Find out how to check here.

Forum Discussion

bph2019's avatar
bph2019
Helpful | Level 6
7 years ago
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 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 .

143 Replies

Replies have been turned off for this discussion
  • Walter's avatar
    Walter
    Icon for Dropbox Community Moderator rankDropbox Community Moderator
    4 years ago

    Hey nei a., sorry to jump in here, but can you clarify what problem you're having with accessing your ticket?

     

    Also, can you confirm that the work-around mentioned here is not working for you?

  • Tom30's avatar
    Tom30
    Collaborator | Level 9
    3 years ago

    Walter when will this finally be solved? Considering the fact that this is open since 2019 with no solution and no workaround (the mentioned one is ridiculous) this should be taken serious and solved instantly. 

  • Walter's avatar
    Walter
    Icon for Dropbox Community Moderator rankDropbox Community Moderator
    3 years ago

    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 .

About Create, upload, and share

Find help to solve issues with creating, uploading, and sharing files and folders in Dropbox. Get support and advice from the Dropbox Community.

The Dropbox Community team is active from Monday to Friday. We try to respond to you as soon as we can, usually within 2 hours.

If you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X, Facebook or Instagram.

For more info on available support options for your Dropbox plan, see this article.

If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!