[Gluster-users] File Corruption with shards - 100% reproducable

Krutika Dhananjay kdhananj at redhat.com
Mon Nov 23 09:44:46 UTC 2015


Thanks Lindsay for the confirmation. 

The patch http://review.gluster.org/#/c/12717/ might just be the fix to the issue you ran into with performance.stat-prefetch on. 
With this patch, it should be possible to enable stat-prefetch without running into any problems. 

-Krutika 

----- Original Message -----

> From: "Lindsay Mathieson" <lindsay.mathieson at gmail.com>
> To: "Krutika Dhananjay" <kdhananj at redhat.com>
> Cc: "gluster-users" <gluster-users at gluster.org>
> Sent: Friday, November 20, 2015 11:56:04 AM
> Subject: Re: [Gluster-users] File Corruption with shards - 100% reproducable

> On 20/11/15 15:15, Lindsay Mathieson wrote:
> > One caveat - I started testing with 3.7.5, then upgraded to 3.7.6, but
> > didn't upgrade the op-version (always forget that).
> >
> > Once I set the op version to 3.7.6 sharded volumes started reporting
> > correct file sizes (for new files) even with strict-write-ordering
> > off. However disk usage was still out by a lot.

> Ignore that, I just retested and file sizes (ls -l) were wildly out.

> However the VM still migrates between nodes with with
> strict-write-ordering off, no problems.

> My apologies for the confusion.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20151123/6f54e2bb/attachment.html>


More information about the Gluster-users mailing list