On 26.04.2013 21:12, Holger Angenent wrote:
Hi,
I faced the problems concerning the conflict files myself, but could
finally solve the problem at least in my installation.
When I upgraded from OC 4.5.x to 5.0.0, I deleted my local synced
directory and let it resync by the client. I think what happened was a
regeneration of the hidden file .csync_journal.db. Since then, no more
conflict files appear in my installation. Other users of the same
installation observed the same.
Did anyone of you tried to do the same? Had this an effect on the problem?
The server update to 5.0.0 unfortunately lost the uniq IDs of the files
on server side, what resulted in having all files suddenly in a "oh,
this has changed" state - for _all_ files.
What the client does in that case is to check if the file has still the
same mtime local and remote. If it has, the files are considered the
same. If not, a conflict file is generated. Unfortunately, two computers
often have a time offset between each other. That is still not much of a
problem, BUT if that time difference is not constant over time, it
becomes more likely that wrong conflicts are generated. So a good hint
is to keep times of all involved machines accurate by using ntp.
From client 1.2.4 on, after having downloaded a potential conflict
file, there is a byte by byte comparison to the original file to check
if they are equal byte wise. If so, no conflict is created. That does
not work for the server side tough.
People keep on asking why we don't use hash values over file contents to
compare. Yes, we could do that. But ownCloud is a very open system that
integrates other technologies, and because of that Frank decided against
that. We would have a hard time to calculate MD5 sums of files which are
mounted into ownCloud from lets say Samba or Dropbox systems. That must
not be forgotten.
We will investigate further on that problem, and I am sure we will be
able to solve it. We understand how annoying and hard to accept this
problem is. Needless to say how important your help is with that.
regards,
Klaas
Am 26.04.2013 13:25, schrieb Jakub Moscicki:
Hello,
I think you are right and this is not update related. We are also
seeing this kind of issues without updating the clients...
On the testpilots mailing list I posted some questions about enabling
logging and reporting problems. We would like to help you debug these
issues and report them in meaningful way. And maybe reproduce them
reliably too...
kuba
--
On Apr 26, 2013, at 12:01 PM, Daniel Molkentin <[email protected]
<mailto:[email protected]>> wrote:
Am 26.04.2013 um 11:57 schrieb hemathor:
i have the exact same experience with the exact same use case almost
every time i update either the owncloud client or the owncloud server.
it is extremely annoying to delete all the conflict files again and
again, sometimes thousands of them, one each minute or so.
Guys, are you really sure this happens when updating the client? Or
is it only that you check after updating it? The client does nothing
special after an upgrade, so it would be a big surprise if the
conflicts were upgrade-related. Also, it would be reproducible, but
it isn't, at least for me.
Daniel
--
www.owncloud.com <http://www.owncloud.com/> - Your Data, Your Cloud,
Your Way!
ownCloud GmbH, GF: Markus Rex, Holger Dyroff
Schloßäckerstrasse 26a, 90443 Nürnberg, HRB 28050 (AG Nürnberg)
_______________________________________________
Owncloud mailing list
[email protected] <mailto:[email protected]>
https://mail.kde.org/mailman/listinfo/owncloud
_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud
_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud
_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud
