<div dir="auto">Not necessarily<div dir="auto">Bitrot could happen even if disk is not totally failed or even if sysadmin change a file directly on the brick, maybe with a broken script or similar</div><div dir="auto"><br></div><div dir="auto">If you corrupt a file the result is the same as bitrot but disk is not failed</div></div><div class="gmail_extra"><br><div class="gmail_quote">Il 1 mar 2017 8:24 AM, "Lindsay Mathieson" <<a href="mailto:lindsay.mathieson@gmail.com">lindsay.mathieson@gmail.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"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 1 March 2017 at 17:15, Gandalf Corvotempesta <span dir="ltr"><<a href="mailto:gandalf.corvotempesta@gmail.com" target="_blank">gandalf.corvotempesta@gmail.<wbr>com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><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"></div></div></blockquote></div><br></div><div class="gmail_extra"><br>Probably because it implies an bigger issues such as disk failure which should be dealt with by an admin<br></div><div class="gmail_extra"><br clear="all"><br>-- <br><div class="m_3158683045825669798gmail_signature" data-smartmail="gmail_signature">Lindsay</div>
</div></div>
</blockquote></div></div>