<div dir="ltr">After a self-heal, mtimes of the two files will be *exactly* the same, because we explicitly set the mtime using utime() call.<div><br></div><div>In normal operations they will differ as much as the time drift between the servers + lag in delivery/issue of write() calls on the servers. This delta is "fixed up" by consistently returning the highest of the two mtimes whenever queried.</div>
<div><br></div><div>Avati</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Oct 25, 2013 at 11:17 AM, James <span dir="ltr"><<a href="mailto:purpleidea@gmail.com" target="_blank">purpleidea@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Fri, Oct 25, 2013 at 1:46 PM, Anand Avati <<a href="mailto:avati@gluster.org">avati@gluster.org</a>> wrote:<br>
> Gluster's replication is synchronous. So writes are done in parallel. If a<br>
> server was down and we self-heal it later, we sync both data and mtime.<br>
<br>
</div>Which is why the mtime of the two files should be the "greatest" of<br>
the mtimes... Is this the case, or rather, what is the case? Will the<br>
two files have the exact same mtime? I actually don't care what the<br>
mtime is, but I think it should be consistent.<br>
</blockquote></div><br></div>