Block-level sync for VeraCrypt not working post 83.4.152 update

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. 

---

Tom30 wrote:

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. 

---

https://www.dropboxforum.com/t5/Files-folders/Block-level-sync-for-VeraCrypt-not-working-post-83-4-152-update/m-p/389929/highlight/true#M141370

Yep.

I have received updates as they roll out. I noticed maybe two days ago that after unmounting my Veracrypt volume the typical indexing was not occuring. I also had, for months, watched midday updates restart Dropbox which would causing a hanging of the syncing since it could not access the mounted Veracrypt volume. But that stopped a few days ago too.

I found this thread, and I'm glad to know there is a workaround. I'm not aware of a downside of the Veracrypt volume modification timestamp being updated. Is there one?

Garrett 

I am not sure if I got you right, but you have the option in regards to timestamp modification ticked of? If so, the downside is, that it takes way longer to sync files, then it would with having that option activated. If you are only synching small files, you will not notice it. If you sync files with 8gb like me, there is a HUGE difference in how long it takes to update files on several devices. 

I use True crypt and was able to get it to sync again by unticking "preserve modification time stamp" but it till took a long time to sync. I notice that the advice from dropbox is that containers with extension .tc will use block level syncing. By default the containers in True crypt have no extension. I added the .tc extention and then tested sync time and it was much faster so I suggest if you haven't added the extension you do so.

Ahh, I see. My entire Veracrypt volume is 10GB. The files inside are smaller, obviously.

I didn't change the extension, and had only noticed a difference in the communicated time remaining on the upload, although in actuality it took as long as before (not long)... maybe a minute.

Man, what a mess these days.

Regarding the .vc and .tc extensions, I read the posts but it appears that DB is saying .tc and .hc extensions.

Confirming .vc is okay, and ...do I just rename the container manually?

(Also discovered my exclusions lists on separate machines no longer works on these...nice to find they are out of space. I knew about the symlinks change but wth.)

Garrett 

Yeah it is a mess, especially getting classified answers by Dropbox members...

I can confirm that containers are working fine with *.vc extension.

Hello John L.2 Julia20 Walter Jane 

does anyone of you still feel reponsible for that topic? It does not look like as no response over than a month. 

Please see the open topics https://www.dropboxforum.com/t5/Files-folders/Block-level-sync-for-VeraCrypt-not-working-post-83-4-152-update/m-p/390001/highlight/true#M141408. 

We still did not get a feedback on what about synching files without .tc and .vc extension.

We still did not get an official statement on the upcoming plans.

Tom30 

Hi Tom30,

Block level sync should be working for all file types, regardless of file extension.  Please let us know if that is not the case.

The issue where changes are not picked up automatically (which is specific to these applications) can be resolved by either turning off the "preserve file modification timestamps" setting in the application or naming the file with a ".tc" or ".hc" extension.

--J

John L.2 

Thanks for your reply. Before the update 83.x it was possible to have the changes being picked automatically, no matter which filetype it was. The current workaround is as suggested by you. I am requesting an option to have the synching of changes available for any extension. This was the case before. 

---

John L.2 wrote:

Tom30 

Hi Tom30,

Block level sync should be working for all file types, regardless of file extension.  Please let us know if that is not the case.

The issue where changes are not picked up automatically (which is specific to these applications) can be resolved by either turning off the "preserve file modification timestamps" setting in the application or naming the file with a ".tc" or ".hc" extension.

--J

---

I just tried yesterday to turn on the "preserve file modification timestamps" setting but it caused the changes not to be picked up. The volume has a .tc extension as directed. For me, it appears not to be "either" but rather "both" still.

John L.2 ...so?

Tom30 

Thanks for your replies/questions here.  We have a ticket open for your request, but do not currently have an ETA for a fix.  Our understanding is that this behavior is very specific to these applications (changes should sync automatically for most other applications since edits will change the modification time), but please let us know if that is not what you are seeing.

John L.2 Hi, thanks your reply.

Can you be more specific on the ticket you have opened? What is the ticket about, ticket description?

I am asking, because I just want to make sure that we talk about the same issue. 

Thanks,

Thomas

Tom30 

Sure, the ticket is about picking up changes to these files even if 1.) modification timestamps have not changed (i.e. preserve modification timestamps remains checked) and 2.) the files do not end in ".tc" or ".hc".

John L.2 yes, I can confirm these are the issues I see not solved.

That takes too long.

Could someone recommend another service with working blocklevel-sync for .vc/.tc containers?

Thank you very much in advanced.

John L.2 Hi, any update on this? I have confirmed the ticket content. When can we expect a fix for synching containers with any file-containers? This is still a BLOCKER. Please let me know the next steps.

BTW: I have a filed with *.vc extension and I am still (since many updates) experiencing issues: Sometimes if the content of the *.vc file is changed, the changes are not directly uploaded to Dropbox. Sometimes this needs a restart of the dropbox client in advance. This is really annoying and is not ok if you do not always remember that issue and you then again end up with 2 files that you have to merge on and on again. 

John L.2 ?

Hi,

I've just recently started having a problem with syncing veracrypt files on windows 10. I've used this setup for a long time and no issues until recently.

I have a veracrypt container I keep in my dropbox folder. Usually if I open it, makes changes to files within it, then close the container, dropbox will sync the container.

However starting just recently, I can make changes to the file within the container, close the container but dropbox will not sync.

If I then open the container on a different computer, I end up with conflicting files.

Can anyone offer suggestions?

Thanks

Jon

Hi there jonb1, thanks for reaching out to us here!

I've just moved your post here as it seems that you're having a similar issue as described here.

Could you check out this post from John and let us know what you find?

Keep us posted!

as it is sitll not properly fixed, any timeline?