<div dir="ltr">Gluster does have logic to always show mtime which is the highest in value. It is probably a bug if you are witnessing different mtimes at different times when no writes have happened in between.<div><br></div>
<div>Avati</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Oct 24, 2013 at 4:31 PM, 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 Thu, 2013-10-24 at 13:00 -0700, Robert Hajime Lanning wrote:<br>
><br>
> Design philosophy...<br>
><br>
> There is no metadata server. When you look at timestamps in stat,<br>
> you<br>
> are seeing the real stat of the file.<br>
</div>So this raises an interesting point...<br>
<div class="im"><br>
><br>
> If you have "replica 2" then you have two files. The stat can come<br>
> from<br>
> either one. Mtime will be the modification time of the file<br>
</div>If the replica N files all have slightly different mtimes (it seems they<br>
usually will because they weren't written at exactly the same time),<br>
then isn't this a point of inconsistency for a script running on a fuse<br>
mount which expects the same mtime on a file?<br>
<br>
Shouldn't gluster somehow coordinate to set all the files mtimes to be<br>
consistent to say the last mtime in the replica set?<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
> referenced<br>
> by the time on the server (not the client.)<br>
><br>
> One of the strengths of GlusterFS is that it does not have the<br>
> bottleneck/single point of failure of a single metadata server.<br>
<br>
</div></div><br>_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a><br></blockquote></div><br></div>