search

smallswan399 / onesync

Automatically exported from code.google.com/p/onesync
0 stars 0 forks source link

Conflict detection weirdness #156

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Syncing my music collection between job <=> home using a HDD.
2. Getting random conflicts with files that did not change at all.

What is the expected output? What do you see instead?
Music library not filling up with conflicting copies.

What version of the product are you using? On what operating system?
OneSync 3 on Windows 7 64-bit

Please provide any additional information below.
Please find attached screen shots.

Original issue reported on code.google.com by Alain.Mi...@gmail.com on 13 Dec 2011 at 8:41

Attachments:

GoogleCodeExporter commented 9 years ago 
One thing to add:

OneSync keeps copying large quantities of files I did not touch at all back and 
forth. With it filling up the intermediate device to such extent it is not much 
smaller in size than the folders on both PC.

I would love to see your software shine, but sadly it is too unreliable in its 
current state. Or maybe at least not as fool proof as it could be, in case it 
is just me. ;-)

For now, I am going back to RoboCopy.

Original comment by Alain.Mi...@gmail.com on 13 Dec 2011 at 9:14

GoogleCodeExporter commented 9 years ago 
I did some research myself on my second issue.

I have searched the SQLite intermediate database file for one of the music 
files which OneSync wants to sync from the intermediate device to my job 
computer. This file has not been changed for a while, just like most of the 
files which are on the intermediate device.

The strange thing is that both the HASH CODE and the LAST MODIFIED TIME are 
equal for both SOURCE IDs. A sync should not be applicable at all.

I have attached the database file to this comment.

Could this be related to my job PC being part of a domain?

Original comment by Alain.Mi...@gmail.com on 14 Dec 2011 at 9:10

Attachments: