lchoquel
-
Posts
7 -
Joined
-
Last visited
-
Days Won
1
Posts posted by lchoquel
-
-
Update: I have reproduced the bug in a simpler, more controlled environment and a simple pattern and I have clean logs. I'll send it in a few minutes.Meanwhile, note that the bug occurred only when my laptop was using Wifi, not using ethernet :-/-------Hi,I've been having the same issue for weeks, stably reproduced. Here's how:
- The base set-up is my office LAN with two PCs running Windows 7, one is a desktop and the other a laptop (actually it's a mac running Windows 7 thru Parallels but that shouldn't be an issue). Everyday we are synching a dozen files weighing between a few MB to over 1GB. Everyday the files are updated by a scheduled process running on the desktop during the night.
- For practical reasons (slow connection), if the laptop is not in the office, I won't use BTSync. Actually it won't even be running on my laptop. Instead, the desktop will upload the latest versions of the files to dropbox (on totally separate folders, so there is no interaction with BTSync here). Then, on the laptop (out of office) I will get the update from dropbox and replace the files in the BTSynched folder.
- So the desktop would have, say, version 5 of the files and now, thanks to Dropbox, the laptop also has version 5.
- Next day, I come into the office and the desktop's scheduled process has updated its files to version 6 during the night. These version 6 files have a modification date during the night, they are of course more recent than my laptop files which are version 5 from the previous nightly update. I open my Laptop, connect to the LAN, fire up BTSync and hope to see my version 5 files replaced by the desktop's version 6 files. But the synch is done the other way.
Everytime I reproduce the same procedure, I will systematically see my laptop's outdated files (version 5) replace the desktop's more recent files (version 6).Do you need logs from the 2 computers reproducing the issue?
- The base set-up is my office LAN with two PCs running Windows 7, one is a desktop and the other a laptop (actually it's a mac running Windows 7 thru Parallels but that shouldn't be an issue). Everyday we are synching a dozen files weighing between a few MB to over 1GB. Everyday the files are updated by a scheduled process running on the desktop during the night.
-
Yes both machines are running Windows 7.
One of them is actually Wndows 7 based on parallels desktop on a Mac but that shouldn't influence the bug.
-
That's it, today the problem happened again but this time on existing files and even on files which had not even changed on either computer.
As a consequence, in some of my synched folders, all or almost all files show the last sync's date instead of their real modification date.
-
I did a few tests and it appears the date bug only concerns new files:
- Existing files updated by sync get the proper modification date synched from original to copy.
- New files get a new date set precisely when the transfer starts, on both sides of the sync.
I haven't reproduced the "re-synch same file back" bug yet.
- Existing files updated by sync get the proper modification date synched from original to copy.
-
I noticed that my PC would slow down when synching very fast over LAN, for instance when it gets above 1.5MB/s.
So I tried reducing the limit on Download and Upload rate: the setting is apparently not taken into account, even several minutes after clicking "Apply".
Bug seen on Windows 7.
-
Great job on SyncApp, I love it. using it everyday with large files synch between two Windows 7 PCs.
I have a issue regarding the "Modification date" set for files received by SyncApp: they are all set to the date of the synch, instead of indicating the same modification date as the original file.
This entails 2 problems:
- I have lost valuable information about the file. I don't know how recent the file actually is. For instance I can't compare the synched file to another version of the file that I might have generated locally in a different folder. FYI DropBox does it well, because it synchs the modification dates properly.
- I'm not 100% sure that it's related to modification dates but: sometimes SyncApp apparently does not realize it's the same file as on the device where the original file was. In some cases SyncApp will re-synch the same file back to the original copy. I really mean sometimes: all files in the folder are not concerned, and it does not go into endless ping-pong mode between the 2 devices. I haven't tested enough to nail it down exactly but part of the pattern might be to kill and relaunch SyncApp, or maybe removing and re-adding the folder to synch.
- I have lost valuable information about the file. I don't know how recent the file actually is. For instance I can't compare the synched file to another version of the file that I might have generated locally in a different folder. FYI DropBox does it well, because it synchs the modification dates properly.
Bad Sync? Overwriting Newer Files
in Sync Troubleshooting
Posted