<div dir="auto">Why not automate this or adding a command that does heal automatically when corruption is found?<div dir="auto"><br></div><div dir="auto">Nobody wants corrupted files on the storage, why you don't heal automatically?</div><div dir="auto"><br></div><div dir="auto">Something like</div><div dir="auto"><br></div><div dir="auto"><pre style="font-family:menlo,monaco,"courier new",monospace;font-size:0.9em;padding:15px;margin-top:0px;margin-bottom:1.8em;line-height:inherit;word-wrap:break-word;background:rgb(51,51,51);border:1px solid rgb(26,26,26);border-radius:0px;white-space:pre-wrap;vertical-align:baseline;color:rgb(240,240,240)!important">gluster volume bitrot <em style="border:0px none;font-size:13.86px;font-variant:inherit;font-weight:inherit;line-height:inherit;margin:0px;padding:0px;vertical-align:baseline">VOLNAME</em> heal start</pre></div></div><div class="gmail_extra"><br><div class="gmail_quote">Il 1 mar 2017 7:32 AM, "Sweta Anandpara" <<a href="mailto:sanandpa@redhat.com">sanandpa@redhat.com</a>> ha scritto:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Bitrot has a scrub process which detects the corrupted file. Once detected, it is the prerogative of the user to follow the sequence of steps [1] to trigger a heal. Having said that, client access to that file is not impacted as it continues to serve data from the good copy.<br>
Steps remain the same irrespective of a replica 2 or replica 3 volume.<br>
<br>
[1] <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html/Administration_Guide/ch20s03.html" rel="noreferrer" target="_blank">https://access.redhat.com/docu<wbr>mentation/en-US/Red_Hat_Storag<wbr>e/3.1/html/Administration_<wbr>Guide/ch20s03.html</a><br>
<br>
Thanks,<br>
Sweta<br>
<br>
On 02/28/2017 06:28 PM, Gandalf Corvotempesta wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
In a replica 3, what happens in case of bit-rot detection on a file ?<br>
Is gluster smart enough to detect this and automatically heal the<br>
corrupted files from other replicas ?<br>
What if in case of replica 2 ? How do know know which is right,<br>
server1 or server2, without a quorum ?<br>
<br>
What if the underling FS (like ZFS) is retuning an error in case of<br>
bit-rot ? ZFS should return an error if file is corrupted (and has not<br>
RAID to recover from), thus gluster should see the file as<br>
missing/corrupted and automatically trigger selfheal from other<br>
replicas ?<br>
______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/gluster-users</a><br>
</blockquote>
<br>
</blockquote></div></div>