marqox

@GreatMarko - point 1 (BTSync version) - it was already like that, point 2 (clocks) - not an issue as mentioned before, point 3 (delete sync temp files) - I will try that, but I think ChrisH is on to something, @ChrisH - actually my case also fits to your description. I got older files from PC that got BTSync program updated to new version.

Update on this issue. Happened again today to me, with BTSync latest version 1.1.127. BTSync again decided for some files that older copies are the "current" versions. This time it was a couple of .doc files and a .xls again. Debug logging mode is on and on one machine sync.log is useless - has a 117 MB with showing just last 10 minutes of records (9133 useful lines and rest huge whitespaces), so no real help from it (the issues happened hours ago).

If it would help, I had to go through versioning history of all files, so have some more details as follows: Files were originally copied 10 days back. On BTSync syncing today, all new files (younger than 10 days) were copied OK, but the 4 files which were updated in meantime were wrongly synced. Since there were actually 4 error messages from the log quoted above (on the "newer" machine), 2 IO Errors and 2 ReadFile Errors, if they are actually 4 separate incidents, not 2, it may give hints on the underlying issue. And BTW, all 4 of those were XLS files. Also I am certain that for sure not all those 4 XLS were open at the time of the errors.

I am not 100% sure, but I think not. For sure no MS Excel was open (I don't have it in these machines), only potentially Open Office (and I think it does not lock xls files, but rather writes a hidden .~lock* file to inform other OO instances about that). At that time I was setting up BitSync folders, so I do not think I was doing anything with those XLS sheets in Open Office anyway.

Likely this is not related, but posting it, just in case. I just noticed in the sync.log an IO error for some of those files which were overwritten: [2013-06-02 12:35:18] IO Error:1168 line:390 align:-99 pos:-99 count:16384 actual:14848 [2013-06-02 12:35:18] ReadFile error: Name1.xls:0:16384:16384:3 [2013-06-02 12:35:18] IO Error:1168 line:390 align:-99 pos:-99 count:16384 actual:10240 [2013-06-02 12:35:18] ReadFile error: Name2.xls:0:16384:16384:3 I wrote that it is likely not related because there are more files which were overwritten which don't have an IO error, only two above have this entry in the log.

First suggestion - not an issue, machine clocks are almost identical and the timestamp difference between files was a matter of weeks. Second suggestion - it is difficult to take that step back, currently (after the issue already happened) there are no .!Sync files anywhere.

Same situation here. Older folders were on Linux Mint machine. Newer folders were on Windows 7. Older files which were x-copied to the Linux machine few weeks back overwrote newer files after Sync 1.0.134 was installed on both. I don't have the time now to reproduce this with logs, I need to invest the time to take a step back (fortunately, files are still versioned by Cubby. Was planning to abandon it, but looks like Sync needs some more stability). I imagine reproducing the problem would be relatively easy, just xcopy something, change it on one side and after that start-up Sync on both machines.