Re: File Corruption with shards - 100% reproducable

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Lindsay,

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?
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.
I want to know if it is *really* necessary in VM workloads.

-Krutika


From: "Lindsay Mathieson" <lindsay.mathieson@xxxxxxxxx>
To: "Krutika Dhananjay" <kdhananj@xxxxxxxxxx>
Cc: "gluster-users" <gluster-users@xxxxxxxxxxx>
Sent: Sunday, November 15, 2015 11:39:57 AM
Subject: Re: File Corruption with shards - 100% reproducable


On 15 November 2015 at 13:32, Krutika Dhananjay <kdhananj@xxxxxxxxxx> wrote:
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.

Yes, that seems to be the guilty party. When disabled I can freely migrate VM's, emabled, things rapidly go pear shaped.


--
Lindsay

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux