JM,<br><br>OK, so what _is_ the correct place then. There is no rhss mailinglist on the <a href="http://www.redhat.com/mailman/listinfo">redhat mailing list page</a>...<br><br>Anyways, I will repost in the gluster-devel mailing list<br clear="all">
<br>Met vriendelijke groeten,<br><b><br><font style="color:rgb(51,102,255)" color="#000099">Fre</font><font style="color:rgb(51,102,255)" color="#000099">d van Zwieten</font><br style="color:rgb(51,102,255)"></b>
<div><font color="#3333ff"><span style="COLOR:rgb(0,0,153)"><b style="color:rgb(51,102,255)">Enterprise Open Source Services</b><br></span></font></div>
<div><b><br><span style="color:rgb(51,102,255)">Consultant</span></b><br><font size="1"><i>(vrijdags afwezig)</i></font></div>
<div><br><b><span style="COLOR:rgb(255,0,0)">VX Company IT Services B.V.</span></b><br><span style="COLOR:rgb(0,0,153)"><b><span style="COLOR:rgb(255,0,0)">T</span></b><span style="background-color:rgb(255,255,255);color:rgb(255,255,255)"> <span style="color:rgb(51,102,255)">(035) 539 09 50 mobiel (06) 41 68 28 48</span></span></span><span style="background-color:rgb(255,255,255);color:rgb(51,102,255)"></span><br style="COLOR:rgb(0,0,153)">
<span style="COLOR:rgb(0,0,153)"><b><span style="COLOR:rgb(255,0,0)">F</span></b> <span style="color:rgb(51,102,255)">(035) 539 09 08</span></span><br style="COLOR:rgb(0,0,153)"><span style="COLOR:rgb(0,0,153)"><b style="COLOR:rgb(255,0,0)">E</b><span style="color:rgb(51,102,255)"> </span></span><a style="color:rgb(51,102,255)" href="mailto:fvzwieten@vxcompany.com" target="_blank">fvzwieten@vxcompany.com</a><br style="COLOR:rgb(0,0,153)">
<span style="COLOR:rgb(0,0,153)"><b style="COLOR:rgb(255,0,0)">I</b> </span><a style="color:rgb(51,102,255)" href="http://www.vxcompany.com/" target="_blank">www.vxcompany.com</a></div><br>
<br><br><div class="gmail_quote">On Mon, Jul 23, 2012 at 10:23 AM, John Mark Walker <span dir="ltr"><<a href="mailto:johnmark@redhat.com" target="_blank">johnmark@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>Hi Fred,<br><br>If you are interested in hearing more about RHSS, this really isn't the right forum for it. <br><br>However, if you would like to discuss creating a translator for GlusterFS, we would love to talk to you. You should post this to the gluster-devel mailing list - <a href="http://lists.nongnu.org/mailman/listinfo/gluster-devel" target="_blank">http://lists.nongnu.org/mailman/listinfo/gluster-devel</a><br>
<br>Thanks,<br>JM<div><div class="h5"><br><br><br><br>----- Fred van Zwieten <<a href="mailto:fvzwieten@vxcompany.com" target="_blank">fvzwieten@vxcompany.com</a>> wrote:<br>> Hi there,<br><div>I am working for a customer right now who is considering Red Hat Storage Server. One of the sought-after features there is bit-rot detection, and even better, (semi-automatic) bit-rot restoration.</div>
<br>><br><div>I know RHSS (nor GlusterFS) has this kind of functionality at the moment (correct me if i'm wrong!), but I would like to propose a design for this as a sort of translator that can be stacked on i.e. a (geo) replication translator.</div>
<br>><br><div>Bit-rot detection can be done through check-summing. It should be a very low priority job running on one of the bricks. The job walks the complete file system and, per file, calculates the check-sum, compares it with the stored check-sum (if present, otherwise it stores the check-sum on all involved bricks, because it hasn't been checked before).</div>
<br>><br><div>Bit-rot restoration could be implemented by comparing the check-sums of the replicas. If there is a mismatch, a more thorough check must be performed, like running a check-sum on all replica's for that file again, do a bit-wise compare, or whatever. If the files are still the same, the check-sum(s) must be replaced. If not, there is actual bit-rot detected. Now what to do? Which replica holds the clean version (the thruth?). With an uneven number of replicas one could simply make it a democratic process and have it fully automated. It should however save the to be replaced version in a separate store and notify the admin for verification. Another method would be to just notify the admin and do nothing.</div>
<br>><br><div>The obvious place to store the check-sums would be in the extended attributes, but one could use a database for it.</div><br><div>I have watch the presentation <a href="https://access.redhat.com/knowledge/videos/red-hat-summit-2012-deep-dive-red-hat-storage" style="vertical-align:baseline;line-height:18px;text-align:left;color:#0033cc;font-size:12px;font-family:'Liberation Sans','Trebuchet MS','Bitstream Vera Sans',helvetica,verdana,arial,sans-serif;margin:0px;padding:0px;border:0px" target="_blank">Red Hat Summit 2012 - A Deep Dive Into Red Hat Storage</a> by Jeff Darcy and I know he (and Red Hat) are very keen on extending the number of translators with useful functionality. I am no programmer myself, but would like to get involved in this kind of stuff.</div>
<br>><br><div>Comments are very welcome!</div><br></div></div></div></blockquote></div><br>