<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>Confusion</author><text>The number of commenters that think the KDE sysadmins were stupid enough to not know that &quot;raid isn&apos;t a backup strategy&quot; is depressing. You either didn&apos;t read the article or you haven&apos;t understood it.&lt;p&gt;Git repositories contain redundant information to perform consistency checks. If a bit flips in one of your repos, &lt;i&gt;git fsck&lt;/i&gt; will immediately catch it. The KDE sysadmins thought these consistency checks were triggered when keeping a repository clone in sync and thus any FS level corruption would be caught at the first subsequent attempt to sync.&lt;p&gt;If you think &quot;Gee, if I know this, surely they do?!&quot; then perhaps the answer is: &quot;They probably do and this issue is more subtle than you initially thought. Reread carefully before implying how dumb others were.&quot;</text><parent_chain></parent_chain></comment><story><title>Too Perfect a Mirror</title><url>http://jefferai.org/2013/03/24/too-perfect-a-mirror/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>kurlberg</author><text>&amp;#62;The root of both bugs was a design flaw: the decision that &amp;#62;git.kde.org was always to be considered the trusted, &amp;#62;canonical source.&lt;p&gt;It seems that an even bigger design flaw is that they (still) aren&apos;t doing regular backups.  The mirroring of course provides some redundancy, similar to what raid does, but as they say: &quot;raid is not a backup solution&quot;.</text><parent_chain></parent_chain></comment><story><title>Too Perfect a Mirror</title><url>http://jefferai.org/2013/03/24/too-perfect-a-mirror/</url></story>