<div dir="ltr"><div><div>You can disable it, we were using that option to work around a caching issue earlier.<br></div>That bug has been fixed now.<br><br></div><div># gluster volume set <VOL> performance.strict-write-ordering off<br><br></div>-Krutika<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 14, 2016 at 8:27 AM, Lindsay Mathieson <span dir="ltr"><<a href="mailto:lindsay.mathieson@gmail.com" target="_blank">lindsay.mathieson@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 14 April 2016 at 12:53, Lindsay Mathieson<br>
<span class=""><<a href="mailto:lindsay.mathieson@gmail.com">lindsay.mathieson@gmail.com</a>> wrote:<br>
> With 3.7.6 (and 3.7.7?) with sharded volumes we had to set:<br>
> performance.strict-write-ordering: on<br>
> otherwise we got wildly inconsistent file sizes between node mounts.<br>
> However I've been rechecking it with 3.7.9 and that no longer seems to<br>
> be the case, whcih is good as strict-write-ordering was quite a<br>
> performance hit.<br>
><br>
> Is this the case? has the issue been fixed for 3.7.9?<br>
<br>
<br>
</span>ps. If strict-write-ordering is no longer needed can I just turn it<br>
off? or would I have to recreate the files on the volume?<br>
<br>
thanks,<br>
<div class="HOEnZb"><div class="h5"><br>
--<br>
Lindsay<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
</div></div></blockquote></div><br></div>