mirror of
https://github.com/amadvance/snapraid.git
synced 2026-10-26 19:01:57 -04:00
Auto update
This commit is contained in:
parent
d6de1adeaa
commit
4f90bfa3f7
1 changed files with 40 additions and 9 deletions
49
compare.html
49
compare.html
|
|
@ -63,12 +63,13 @@ It supports both snapshot redundancy and real-time redundancy, with integrity ch
|
|||
<li><a href="http://en.wikipedia.org/wiki/btrfs">Btrfs</a>
|
||||
- OpenSource filesystem GPL2 with real-time redundancy.
|
||||
From Linux 3.9 it supports <a href="http://lwn.net/Articles/536038/">RAID5/6 redundancy</a> and integrity checksums.
|
||||
Recently various issues were found and the official <a href="https://btrfs.wiki.kernel.org/index.php/RAID56">wiki</a> now states:
|
||||
<i>The parity RAID code has multiple serious data-loss bugs in it. It should not be used for anything other than testing purposes.</i>
|
||||
</li>
|
||||
<li><a href="http://blogs.msdn.com/b/b8/archive/2012/01/05/virtualizing-storage-for-scale-resiliency-and-efficiency.aspx">Storage Spaces</a>
|
||||
- The last contender from Microsoft, and integrated into Windows 8.
|
||||
Proprietary with real-time redundancy. Checksumming is not supported, but it could be provided by
|
||||
<a href="http://blogs.msdn.com/b/b8/archive/2012/01/16/building-the-next-generation-file-system-for-windows-refs.aspx">ReFS</a>.
|
||||
But with some <a href="http://helgeklein.com/blog/2012/03/windows-8-storage-spaces-bugs-and-design-flaws/">limitations</a>.
|
||||
Proprietary with real-time redundancy. Checksumming is not supported.
|
||||
It also has some other <a href="http://helgeklein.com/blog/2012/03/windows-8-storage-spaces-bugs-and-design-flaws/">limitations</a>.
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
|
@ -99,7 +100,7 @@ snapshot at request time, like Backup.</td>
|
|||
<tr><td><span class="bold">Integrity</span><br>
|
||||
If data is validated with some kind of checksum,
|
||||
and which one is the default.</td>
|
||||
<td>Yes<br>SpookyHash<br>128 bit</td><td>No</td><td>Yes<br>Adler32<br>32 bit</td><td>Yes<br>fletcher4<br>256 bit</td><td>Yes<br>CRC32C<br>32 bit</td><td>No</td></tr>
|
||||
<td>Yes<br>SpookyHash<br>128 bit</td><td>No <a href="#note8">[8]</a></td><td>Yes<br>Adler32<br>32 bit</td><td>Yes<br>fletcher4<br>256 bit</td><td>Yes<br>CRC32C<br>32 bit</td><td>No <a href="#note9">[9]</a></td></tr>
|
||||
|
||||
<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>
|
||||
|
|
@ -130,10 +131,13 @@ http://www.openegg.org/forums/posts/list/727.page
|
|||
<tr><td><span class="bold">Number of failures</span><br>
|
||||
How many disk failures are supported? 1 is for RAID5, 2 for RAID6.
|
||||
</td>
|
||||
<td>1 2 3 4 5 6</td><td>1 2</td><td>1 2 3 4 5 6+</td><td>1 2 3</td><td>1 2</td><td>1</td></tr>
|
||||
<td>1 2 3 4 5 6</td><td>1 2</td><td>1 2 3 4 5 6+</td><td>1 2 3</td><td>1 2</td><td>1 2</td></tr>
|
||||
|
||||
<!---
|
||||
unRAID 6.2 adds Dual parityvs ZFS
|
||||
|
||||
New Storage Spaces adds Dual Parity if you have at least 7 disks
|
||||
https://blogs.technet.microsoft.com/tip_of_the_day/2014/07/23/tip-of-the-day-dual-parity-storage-spaces/
|
||||
-->
|
||||
|
||||
<tr><td><span class="bold">Other failures</span><br>If more disks fail than the supported redundancy model,
|
||||
|
|
@ -158,7 +162,7 @@ http://serverfault.com/questions/190207/how-can-i-add-one-disk-to-an-existing-ra
|
|||
<td>Linux<br>Windows<br>Mac OS X<br>OpenIndiana<br>Solaris<br>BSD</td><td>Linux</td><td>Windows<br>Linux</td><td>Linux <a href="#note6">[6]</a><br>Mac OS 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>2005</td><td>2013</td><td>2012</td></tr>
|
||||
<td>2011</td><td>2005</td><td>2008</td><td>2005</td><td>not yet stable <a href="#note11">[11]</a></td><td>2012</td></tr>
|
||||
|
||||
<!---
|
||||
ZFS 2009 is the data of the "Triple-Parity RAID-Z" article by Adam Leventhal
|
||||
|
|
@ -171,13 +175,13 @@ http://www.eecs.berkeley.edu/Pubs/TechRpts/1987/5853.html
|
|||
<tr><td><span class="bold">License/Price</span><br>
|
||||
Software license and price.
|
||||
</td>
|
||||
<td>Open Source GPL3<br>Free</td><td>Open Source GPL2<br>89$/129$</td><td>Proprietary<br>40$/60$</td><td>Open Source CDDL<br>Free</td><td>Open Source GPL2<br>Free</td><td>Proprietary<br>Windows 8</td></tr>
|
||||
<td>Open Source GPL3<br>Free</td><td>Open Source GPL2<br>89$/129$</td><td>Proprietary<br>40$/60$</td><td>Open Source CDDL<br>Free</td><td>Open Source GPL2<br>Free</td><td>Proprietary<br>Windows 8/10</td></tr>
|
||||
|
||||
<tr><td><span class="bold">Interface</span><br>Which interface is provided? GUI or command line?</td>
|
||||
<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<br>GUI/Plugins <a href="#note7">[7]</a></td><td>command line</td><td>GUI</td></tr>
|
||||
</td><td>command line<br>GUI</td><td>GUI</td><td>command line<br>GUI/Plugins <a href="#note7">[7]</a></td><td>command line<br>GUI<a href="#note10">[10]</a></td><td>GUI</td></tr>
|
||||
|
||||
</table>
|
||||
|
||||
|
|
@ -223,7 +227,8 @@ always using the best known RAID algorithm and implementation.
|
|||
|
||||
<p>
|
||||
<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.
|
||||
formatted with the ReiserFS, XFS or Btrfs filesystems.
|
||||
But not ext4 or NTFS, the two most common filesystems used in Linux and Windows.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -240,6 +245,32 @@ See <a href="http://louwrentius.com/the-hidden-cost-of-using-zfs-for-your-home-n
|
|||
and plugins for <a href="http://www.freenas.org/">FreeNAS</a> and <a href="http://www.nas4free.org/">NAS4Free</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<a id="note8">[8]</a> - unRAID can have integrity checksum using a plugin like
|
||||
<a href="https://forums.lime-technology.com/topic/43290-dynamix-file-integrity-plugin/">Dynamix File Integrity</a>,
|
||||
<a href="https://forums.lime-technology.com/topic/41708-checksum-suite/">Checksum Suite</a> or
|
||||
<a href="https://forums.lime-technology.com/topic/35615-bunker-yet-another-utility-for-file-integrity-checks/">bunker</a>
|
||||
but they are all independent at the parity processing.
|
||||
For example, you need two independent scrub processes to verify both integrity and parity.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<a id="note9">[9]</a> - Storage Spaces can be used with ReFS that support integrity checksum, but not in the Parity mode:
|
||||
<a href="http://www.windowscentral.com/how-use-resilient-file-system-refs-windows-10"><i>"Although, you may be able to select Simple (no resiliency) or Parity, both of these options will fail the process"</i></a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<a id="note10">[10]</a> - Btrfs has external GUIs, like <a href="http://rockstor.com/">Rockstor</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<a id="note11">[11]</a> - Btrfs supports RAID5 from 2013, but recently some serious issues in the
|
||||
RAID5/6 support were <a href="https://www.phoronix.com/scan.php?page=news_item&px=Btrfs-RAID-56-Is-Bad">found</a>.
|
||||
At present they <a href="https://www.phoronix.com/scan.php?page=news_item&px=Btrfs-RAID56-Not-All-Clear">aren't fixed yet</a>.
|
||||
The official wiki says:
|
||||
<a href="https://btrfs.wiki.kernel.org/index.php/RAID56"><i>"The parity RAID code has multiple serious data-loss bugs in it. It should not be used for anything other than testing purposes"</i></a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
If you think that some information reported is incorrect or simply unfair, please report it in the <a href="https://sourceforge.net/p/snapraid/discussion/1677233/">Forum</a>.
|
||||
</p>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue