[Reposting here with Nicholas' permission] On Mi, 2010-02-24 at 07:01 +0000, Nicholas Goodwin wrote: This is indeed bad. I haven't heard of this problem before. Regarding working around this as you suggested: we could do it in a similar way as the "preventSlowSync" option. With sync property "preventClearPeer=1" set (default), a sync which removes all items from a peer is not allowed to proceed, with a suitable error message. To proceed, the user would then have to pick a sync mode as in the "preventSlowSync" case (slow, refresh from server/client) or run a two-way sync with "preventClearPeer=0". Better names for "preventClearPeer" welcome. A log would be interesting, although I doubt that it will tell us anything about this EDS failure. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.