<div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span style="font-size:12.8px">> I've been seeing a great many errors like this on both sides:<br></span><span style="font-size:12.8px">><br></span><span style="font-size:12.8px">> While syncing file<br></span><span style="font-size:12.8px">> /var/www/htdocs/wp-content/</span><span style="font-size:12.8px">themes/wireframe/widgets/</span><span style="font-size:12.8px">search_widget.php:<br></span><span style="font-size:12.8px">> ERROR from peer server1: File is also marked dirty here!<br></span><span style="font-size:12.8px">> Do not auto-resolve conflict: Lost 'younger/older' test.</span> </blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"> </blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span style="font-size:12.8px">So why is that file generated simultaneously on both nodes?</span></blockquote><div><br></div><div>In case my question wasn't clear: the file is identical on both sides because csync2 synchronised it, and adjusted the copy's dates as it did. No other process would be capable of producing an exactly identical timestamp.</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><b><font color="#660000">Marcus Downing</font></b><div><a href="mailto:marcus@bang-on.net" target="_blank">marcus@bang-on.net</a></div><div><br></div></div></div></div>
<br><div class="gmail_quote">On 3 November 2015 at 11:07, Marcus Downing <span dir="ltr"><<a href="mailto:marcus@bang-on.net" target="_blank">marcus@bang-on.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><span class=""><div class="gmail_quote">On 3 November 2015 at 11:00, <span dir="ltr"><<a href="mailto:csync2-request@lists.linbit.com" target="_blank">csync2-request@lists.linbit.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="overflow:hidden">If the stat information (as recorded by csync2) is identical,<br>
*and* the content is identical, even if both sides are "marked dirty",<br>
You will get "File is already up to date on peer.",<br>
and the dirty flag is cleared (on both sides, for this host pair).<br>
<br>
At least that is how it *should* be, and how it works for me.<br>
So if that does not work for you, you may need to upgrade,<br>
or come back with a test case to show how to reproduce the misbehaviour.</div></blockquote></div><br></span>That's what I'd expect to happen but isn't.</div><div class="gmail_extra"><br></div><div class="gmail_extra">I'll try upgrading and see if it changes anything.</div><span class="HOEnZb"><font color="#888888"><div class="gmail_extra"><br><br clear="all"><div><div><div dir="ltr"><b><font color="#660000">Marcus Downing</font></b><div><a href="mailto:marcus@bang-on.net" target="_blank">marcus@bang-on.net</a></div><div><br></div></div></div></div>
</div></font></span></div>
</blockquote></div><br></div>