Syncing Pre-existing Folders in 2.3.6

[chicagonyc]

I have BTsync 2.3.6 installed on a variety of Windows 8.1 x64 machines, and it's worked fine since I upgraded from 1.4. I have a large collection of folders that I sync successfully, some very large (nearly 200 Gb).

I installed BTsync 2.3.6 on a new Windows 10 x64 machine, and I copied all my files from my old computer to the new one. I knew that BTsync is good about not re-transfering identical data, so I just added all the folders to the new machine and let them go about re-indexing. Everything went perfectly for every single folder save one. This one has about 80k files and 77 Gb of data. I have let the indexing process go on for days but it doesn't seem to end. I do see in the size column that it rapidly went up to the 77Gb size of the folder.

In the sync window, all of my other folders say "synced xx minutes ago", while this one says "synced xx days ago". But actually, it's not synced; I add files to the equivalent folder on my other machines and it doesn't come over. 

There are two things that I can think of that distinguishes this particular folder. One is the number of files: my other folders might be larger, but none have this quantity of files. Then again, I have no problem syncing this volume of files beyond this particular Win10 machine.

The second is that I tried to "add the folder" using the right click context menu item that came up after installing BTsync 2.3.6. I thought it was a shortcut to doing this manually within the program. Then BTsync complained about some files being missing and needing to re-start indexing from scratch. I let it do so. Just to be safe, I removed the folder and re-added it. I did this twice, and let it run for days each time.

What can/should I do now?

[Remirus]

chicagonyc, we received your ticket with logs. Let's continue our discussion in the support system.

[Remirus]

According to the logs it happened because of old bug which appeared in 2.2.1 version. It was fixed in 2.2.5 so it shouldn't happen again.

However, if it is was caught in 2.2.1 version before the fix, it is necessary to update modification time of the file on which Sync stooped synchronization. In the logs there will "failed to verify signature" message with the file name.

[chicagonyc]

Remirus was super helpful. I basically looked through the logs and saw some temp files which " failed to verify signature ".

I just deleted them. Once I did that the sync worked perfectly.

I'm not sure about the version though. I had 1.4 before upgrading to 2.3.6.

I do still have the bug on another folder I'm trying to sync. Here, the failed to verify signature is attached to a folder, not a bunch of temp files.