[Gluster-devel] BitRot notes

[Alok Srivastava]

Thanks Venky for sharing the details.
I have included Pranith and Atin for a specific question:

With current implementation of erasure coding, Do we  have the capability of detecting and correcting bit rot? 

Let's say we have fragments of a file on multiple bricks and a read request is sent to the bricks, a brick  doesn't respond as it may have disk(s) damaged by bit rot or any other failure. Will EC detect and correct bit rot in this case? 

Regards
Alok


----- Original Message -----
From: "Venky Shankar" <vshankar at redhat.com>
To: gluster-devel at gluster.org
Cc: "Vijay Bellur" <vbellur at redhat.com>, "Ric Wheeler" <rwheeler at redhat.com>, "Alok Srivastava" <asrivast at redhat.com>, "Raghavendra Bhat" <rabhat at redhat.com>
Sent: Friday, October 31, 2014 4:09:03 PM
Subject: BitRot notes

Hey folks,

Myself and Raghavendra (@rabhat) have been discussing about BitRot[1] 
and came up with a list of high level tasks (breakup items) captured 
here[2]. The pad will be updated on an ongoing basis reflecting the 
current status/items that are being worked on. As always, contributions 
in any form (design, code, doc, etc..) are more than welcome (just make 
sure you're heard on the pad/email :))

[1]: 
http://www.gluster.org/community/documentation/index.php/Features/BitRot
[2]: https://public.pad.fsfe.org/p/glusterfs-bitrot-notes

Thanks,
venky