<html><body><div style="font-family: garamond,new york,times,serif; font-size: 12pt; color: #000000"><div>Thanks Lindsay for the confirmation.<br></div><div><br></div><div>The patch <a href="http://review.gluster.org/#/c/12717/">http://review.gluster.org/#/c/12717/</a> might just be the fix to the issue you ran into with performance.stat-prefetch on.<br></div><div>With this patch, it should be possible to enable stat-prefetch without running into any problems.<br></div><div><br></div><div>-Krutika<br></div><div><br></div><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Lindsay Mathieson" <lindsay.mathieson@gmail.com><br><b>To: </b>"Krutika Dhananjay" <kdhananj@redhat.com><br><b>Cc: </b>"gluster-users" <gluster-users@gluster.org><br><b>Sent: </b>Friday, November 20, 2015 11:56:04 AM<br><b>Subject: </b>Re: [Gluster-users] File Corruption with shards - 100% reproducable<br><div><br></div><br>On 20/11/15 15:15, Lindsay Mathieson wrote:<br>> One caveat - I started testing with 3.7.5, then upgraded to 3.7.6, but <br>> didn't upgrade the op-version (always forget that).<br>><br>> Once I set the op version to 3.7.6 sharded volumes started reporting <br>> correct file sizes (for new files) even with strict-write-ordering <br>> off. However disk usage was still out by a lot. <br><div><br></div>Ignore that, I just retested and file sizes (ls -l) were wildly out.<br><div><br></div>However the VM still migrates between nodes with with <br>strict-write-ordering off, no problems.<br><div><br></div>My apologies for the confusion.<br></blockquote><div><br></div></div></body></html>