Re: File Corruption with shards - 100% reproducable

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

 



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


From: "Lindsay Mathieson" <lindsay.mathieson@xxxxxxxxx>
To: "Krutika Dhananjay" <kdhananj@xxxxxxxxxx>
Cc: "gluster-users" <gluster-users@xxxxxxxxxxx>
Sent: Friday, November 20, 2015 11:56:04 AM
Subject: Re: 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.

_______________________________________________
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