Auto update

This commit is contained in:
Andrea Mazzoleni 2015-09-09 23:33:37 +02:00
parent 23a556df06
commit 44b11d5d99

View file

@ -46,6 +46,8 @@
<p>
The best known others are:
</p>
<ul>
<li><a href="http://www.lime-technology.com/">unRAID</a>
- Commercial and OpenSource GPL2 solution. A modified version of the Linux Reiserfs filesystem with real-time redundancy.
@ -72,7 +74,6 @@ Proprietary with real-time redundancy. Checksumming is not supported, but it cou
But with some <a href="http://helgeklein.com/blog/2012/03/windows-8-storage-spaces-bugs-and-design-flaws/">limitations</a>.
</li>
</ul>
</p>
<p>
The main factor to categorize them is when the redundancy information is updated.
@ -105,7 +106,7 @@ and which one is the default.
<tr><td><span class="bold">Fix silent errors</span><br/>
If silent errors are detected and fixed before they can propagate into the parity.
<td>Yes</td><td>No <a href="#1">[1]</a></td><td>No <a href="#2">[2]</a></td><td>No</td><td>Yes <a href="#3">[3]</a></td><td>Yes <a href="#3">[3]</td><td>No</td></tr>
<td>Yes</td><td>No <a href="#note1">[1]</a></td><td>No <a href="#note2">[2]</a></td><td>No</td><td>Yes <a href="#note3">[3]</a></td><td>Yes <a href="#note3">[3]</a></td><td>No</td></tr>
<!---
Silent error discussion in UnRAID Forum:
@ -142,7 +143,7 @@ is it possible to recover the data in the not failed disks?</td>
<td>One</td><td>One</td><td>One</td><td>One</td><td>All</td><td>All</td><td>All</td></tr>
<tr><td><span class="bold">Filled disks</span><br/>Can you start with already filled disks?</td>
<td>Yes</td><td>Partial<a href="#4">[4]</td><td>Yes</td><td>Yes</td><td>No</td><td>No</td><td>No</td></tr>
<td>Yes</td><td>Partial<a href="#note4">[4]</a></td><td>Yes</td><td>Yes</td><td>No</td><td>No</td><td>No</td></tr>
<tr><td><span class="bold">Add disks</span><br/>Can you add disks at later time?</td>
<td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td><td>No</td><td>Yes</td><td>Yes</td></tr>
@ -153,7 +154,7 @@ http://serverfault.com/questions/190207/how-can-i-add-one-disk-to-an-existing-ra
-->
<tr><td><span class="bold">Operating system</span><br/>Which OS is supported?</td>
<td>Linux<br/>Windows<br/>Mac&nbsp;OS&nbsp;X<br/>OpenIndiana<br/>Solaris<br/>BSD</td><td>Linux</td><td>Windows<br/>Linux</td><td>Windows</td><td>Linux <a href="#5">[5]</a><br/>Mac&nbsp;OS&nbsp;X<br/>OpenIndiana<br/>Solaris<br/>BSD</td><td>Linux</td><td>Windows</td></tr>
<td>Linux<br/>Windows<br/>Mac&nbsp;OS&nbsp;X<br/>OpenIndiana<br/>Solaris<br/>BSD</td><td>Linux</td><td>Windows<br/>Linux</td><td>Windows</td><td>Linux <a href="#note5">[5]</a><br/>Mac&nbsp;OS&nbsp;X<br/>OpenIndiana<br/>Solaris<br/>BSD</td><td>Linux</td><td>Windows</td></tr>
<tr><td><span class="bold">Age</span><br/>The year of the first official release supporting at least RAID5 redundancy.</td>
<td>2011</td><td>2005</td><td>2008</td><td>2009</td><td>2005</td><td>2013</td><td>2012</td></tr>
@ -175,20 +176,20 @@ Software license and price.
<td>
command line<br/>or <a href="http://elucidate.codeplex.com/">Elucidate</a> GUI,
or plugin for for <a href="http://www.openmediavault.org/">OpenMediaVault</a>
</td><td>command line<br/>GUI</td><td>GUI</td><td>command line</td><td>command line<br/>GUI/Plugins <a href="#6">[6]</a></td><td>command line</td><td>GUI</td></tr>
</td><td>command line<br/>GUI</td><td>GUI</td><td>command line</td><td>command line<br/>GUI/Plugins <a href="#note6">[6]</a></td><td>command line</td><td>GUI</td></tr>
</table>
<h3>Notes</h3>
<p>
<a id="1">[1]</a> - unRAID doesn't have any kind of checksum, and it just ignores silent errors.
<a id="note1">[1]</a> - unRAID doesn't have any kind of checksum, and it just ignores silent errors.
Even worse, if a parity error is detected as result of a silent error in the data,
the parity is automatically recomputed, making impossible to recover the silent error, even manually.
</p>
<p>
<a id="2">[2]</a> - Flexraid uses checksums to validate files, but such checksums
<a id="note2">[2]</a> - Flexraid uses checksums to validate files, but such checksums
<a href="http://forum.flexraid.com/index.php/topic,3233.0.html">are not verified when data is read to update the parity</a>.
This means that any silent error present will propagate into the parity,
making impossible to fix it later, even if it can be still detected comparing the file checksum.
@ -199,7 +200,7 @@ making impossible to fix the errors.
</p>
<p>
<a id="3">[3]</a> - ZFS and Btrfs provide a bit-rot protection at the same level of SnapRAID,
<a id="note3">[3]</a> - ZFS and Btrfs provide a bit-rot protection at the same level of SnapRAID,
always checking data before using it.
In this regards all the three solutions represent the state-of-the-art.
<br/>
@ -220,16 +221,16 @@ always using the best known RAID algorithm and implementation.
</p>
<p>
<a id="4">[4]</a> - unRAID allows to use filled disks but only if they are already
<a id="note4">[4]</a> - unRAID allows to use filled disks but only if they are already
formatted with the ReiserFS, XFS or Btrfs filesystems. But not ext4 or NTFS.
</p>
<p>
<a id="5">[5]</a> - ZFS is also available in Linux at kernel level using <a href="http://zfsonlinux.org/">ZFS on Linux</a>.
<a id="note5">[5]</a> - ZFS is also available in Linux at kernel level using <a href="http://zfsonlinux.org/">ZFS on Linux</a>.
</p>
<p>
<a id="6">[6]</a> - ZFS has external GUIs, like <a href="http://www.napp-it.org/">Napp-it</a>
<a id="note6">[6]</a> - ZFS has external GUIs, like <a href="http://www.napp-it.org/">Napp-it</a>
and plugins for <a href="http://www.freenas.org/">FreeNAS</a> and <a href="http://www.nas4free.org/">NAS4Free</a>.
</p>