andrew_

Followup: I've been messing around inside the above referenced share on one of the two endpoints. I've been busy removing old files, renaming and creating new folders, and moving files from previously existing folders into other/new folders within the hierarchy of that share. One large move of files to a different subfolder sparked a 1.1GB re-transfer of data (how incredibly inefficient). Another folder create, followed by file move from a preexisting subfolder into the newly created folder triggered an apparent re-transfer of that file (6.5 MB), at the conclusion of which the share's syn

I have a share under which I just moved 1.1GB of files out of one subfolder, and into a different subfolder as part of a reclassification of those files. The result of this action was for BTSync to delete these files from the source subfolder on the remote endpoint, then re-transfer them from the local endpoint into their new destination subfolder on the remote endpoint. 1.1GB of data was caused to flow across the network, that didn't strictly need to occur. Tracking moves of files between subfolders, and folder creates/renames/deletes, is something Microsoft's SyncToy can do, so that mini

I notice precisely the same symptom. I have a setup with 11 shares on two endpoint systems. Two of them are "stalled" in this manner, always with a tiny amount (up to just a few tens of kB) left to transfer. The first affected share developed this issue several months ago. The amount remaining on stall is always the same, 7.5 kB, and the perspective (upload/download) is different and appropriate depending on which endpoint you're looking at. The share is bidirectional, with lots of content changing on either side. Sync appears to work correctly, however, despite the reported amount remaining