On 2014-07-23 13:42, Joseph Fernandes wrote: > Hi Anders, > > Currently we don't have an implementation/patch for bit-rot. > We are working on the design of bit-rot protection(for read-only data), as part of Gluster Compliance. read only data is nice for archival (which is why my backups go to CDs/DVDs since 15 years back and bit-rot detection by md5 sums). > Please refer to the Gluster Compliance Proposal > http://supercolony.gluster.org/pipermail/gluster-devel/2014-June/041258.html > > If you have any design proposal/suggestion, please do share, so that we can have a discussion on it. I'm more interested in periodically (or triggered by writes) scan and checksum all/parts of the files on gluster volumes, and compare those checksums between replicas (wont work for open files like databases/VM-images). I'll guess that I put my current tools onto each brick, and whip up some scripts to compare those. When something materializes, I'm interested in testing. > > Regards, > Joe > > ----- Original Message ----- > From: "Anders Blomdell" <anders.blomdell@xxxxxxxxxxxxxx> > To: "Gluster Devel" <gluster-devel@xxxxxxxxxxx> > Sent: Monday, July 21, 2014 10:42:00 PM > Subject: Status of bit-rot detection > > Since switching to xfs have left me with a seemingly working system :-), > what is the current status on bit-rot detection ( > http://www.gluster.org/community/documentation/index.php/Arch/BitRot_Detection), > any patches for me to try? /Anders -- Anders Blomdell Email: anders.blomdell@xxxxxxxxxxxxxx Department of Automatic Control Lund University Phone: +46 46 222 4625 P.O. Box 118 Fax: +46 46 138118 SE-221 00 Lund, Sweden _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-devel
