search

pydio / pydio-sync-java

[DEPRECATED] Synchronization Client of the Pydio project. Based on the Java SDK.
GNU General Public License v3.0
35 stars 15 forks source link

Different timestamp triggers conflict even if file contents identical #5

Closed adrianbj closed 11 years ago

adrianbj commented 12 years ago

The scenario for me was this. One person moved all the files on his desktop into a different folder, leaving the local sync folder empty. This resulted in the deletion of all the files on the server after a sync. I restored the files from our backup server using scp. The copy of the sync tool on my desktop machine hadn't run yet and therefore the original files still existed for me. This resulted in conflict warnings for all the files when attempting to sync.

cdujeu commented 11 years ago

Two problems here : 1/ We should never trigger a deletion of the server files if more than XXX files have been removed without asking (what do you think?) 2/ Normally we try at maximum to avoid false conflicts, by using the files md5, you do have the filehasher installed on your repository?

adrianbj commented 11 years ago

1) I think that sounds like a great safeguard. 2) I have the filehasher plugin enabled, but I don't have Filehasher as a meta source for any of my repositories. Is that what I need to do to make sure each file gets an md5?

cdujeu commented 11 years ago

Yes definitely, add a meta.filehasher to all repositories

adrianbj commented 11 years ago

Yeah - I just started going through them all now, adding it - it's taking a while :)

cdujeu commented 11 years ago

adrian, any news on this? can we close this bug?

adrianbj commented 11 years ago

Thanks for reminding me. I went through and added the filehasher to all repositories, but ended up getting an error. See this post: http://forum.ajaxplorer.info/discussion/4601/fatal-error-when-using-filehasher-plugin/p1

So, unfortunately the answer for now is no as I haven't been able to get the filehasher to work.