<html><body><div style="font-family: garamond,new york,times,serif; font-size: 12pt; color: #000000"><div>Lindsay,</div><div><br></div><div>I wanted to ask you one more thing: specifically in VM workload with sharding, do you run into consistency issues with strict-write-ordering being off?</div><div>I remember suggesting that this option be enabled. But that was for plain dd on the mountpoint (and not inside the vm), where it was necessary.<br></div><div>I want to know if it is *really* necessary in VM workloads.<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>Sunday, November 15, 2015 11:39:57 AM<br><b>Subject: </b>Re: [Gluster-users] File Corruption with shards - 100% reproducable<br><div><br></div><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 15 November 2015 at 13:32, Krutika Dhananjay <span dir="ltr"><<a href="mailto:kdhananj@redhat.com" target="_blank">kdhananj@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">So to start with, just disable performance.stat-prefetch and leave the rest of the options as they were before and run the test case.</blockquote></div><br></div><div class="gmail_extra">Yes, that seems to be the guilty party. When disabled I can freely migrate VM's, emabled, things rapidly go pear shaped.<br></div><div class="gmail_extra"><br clear="all"><br>-- <br><div class="gmail_signature">Lindsay</div>
</div></div>
</blockquote><div><br></div></div></body></html>