Auto update

compare.html

@@ -92,7 +92,7 @@ and if <span class="bold">all your disks are spinning when reading one file</spa
 </p>
 
 <table class="compare">
-<tr><th></th><th><span class="bold">SnapRAID</span></th><th>unRAID</th><th>FlexRAID</th><th>disParity</th><th>ZFS</th><th>Btrfs</th><th>Storage Spaces</th></tr>
+<tr><th width="30%"></th><th><span class="bold">SnapRAID</span></th><th>unRAID</th><th>FlexRAID</th><th>disParity</th><th>ZFS</th><th>Btrfs</th><th>Storage Spaces</th></tr>
 
 <tr><td><span class="bold">Redundancy model</span><br/>Real-time computes parity at real-time like RAID,
 snapshot at request time, like Backup.</td>
@@ -141,9 +141,17 @@ is it possible to recover the data in the not failed disks?</td>
 <tr><td><span class="bold">Power/Noise</span><br/>How many disks are spinning when reading a single file?</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 disk</span><br/>Can you start with already filled disks?</td>
+<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>
 
+<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>
+
+<!--
+ZFS does't allow to add new disks to a raidz pool
+http://serverfault.com/questions/190207/how-can-i-add-one-disk-to-an-existing-raidz-zpool
+-->
+
 <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>
 
@@ -152,6 +160,10 @@ is it possible to recover the data in the not failed disks?</td>
 
 <!---
 ZFS 2009 is the data of the "Triple-Parity RAID-Z" article by Adam Leventhal
+
+RAID 1987 is the date of the paper:
+"A Case for Redundant Arrays of Inexpensive Disks (RAID)", David A. Patterson, Garth A. Gibson and Randy H. Katz
+http://www.eecs.berkeley.edu/Pubs/TechRpts/1987/5853.html
 -->
 
 <tr><td><span class="bold">License/Price</span><br/>

download.html

@@ -50,19 +50,16 @@ If you like to use a GUI, you can try <a href="http://elucidate.codeplex.com/">E
 <table class="download">
 <tr><th>File</th><th>Description</th></tr>
 <tr><td>
-<!-- http://sourceforge.net/projects/snapraid/files/snapraid-8.1.tar.gz/download -->
 <a href="https://github.com/amadvance/snapraid/releases/download/v8.1/snapraid-8.1.tar.gz">snapraid-8.1.tar.gz</a>
 </td><td>
 Sources for Linux, Mac OS X, BSD, Solaris, OpenIndiana and any other Unix
 </td></tr>
 <tr><td>
-<!-- http://sourceforge.net/projects/snapraid/files/snapraid-8.1-windows-x64.zip/download -->
 <a href="https://github.com/amadvance/snapraid/releases/download/v8.1/snapraid-8.1-windows-x64.zip">snapraid-8.1-windows-x64.zip</a>
 </td><td>
 Binaries for Windows x64 (the most recent Windows versions)
 </td></tr>
 <tr><td>
-<!-- http://sourceforge.net/projects/snapraid/files/snapraid-8.1-windows-x86.zip/download -->
 <a href="https://github.com/amadvance/snapraid/releases/download/v8.1/snapraid-8.1-windows-x86.zip">snapraid-8.1-windows-x86.zip</a>
 </td><td>
 Binaries for Windows x86

faq.html

@@ -157,9 +157,28 @@ RAIDs are mirroring solutions that propagate changes immediately to the parity d
 In this sense, RAIDs are not backups, because they don't allow to restore an old state of the array.
 </p>
 <p>
-SnapRAID is instead more similar at a backup solution, and you can restore the state of the last backup made.
+SnapRAID is instead more similar at a backup solution, and you can restore the state of the last backup.
 For example, with SnapRAID, if you delete by accident a file, you can easily restore it.
 </p>
+<p>
+Others advantages over traditional RAID5/6 solutions are:
+<ul>
+<li>All your data is hashed to ensure data integrity and to avoid silent corruption.</li>
+<li>If the failed disks are too many to allow a recovery, you lose the data only on the failed disks.
+All the data in the other disks is safe.</li>
+<li>If you accidentally delete some files in a disk, you can recover them.</li>
+<li>You can start with already filled disks.</li>
+<li>The disks can have different sizes.</li>
+<li>You can add disks at any time.</li>
+<li>It doesn't lock-in your data. You can stop using SnapRAID at any time
+without the need to reformat or move data.</li>
+<li>To access a file, a single disk needs to spin, saving power and
+producing less noise.</li>
+<li>You can have up to six parity levels compared to the one of RAID5 and the two of RAID6.</li>
+</ul>
+Obviously RAID has other advantages, like having a better speed due data striping.
+What is best for you, depends on your specific use case.
+</p>
 
 <a id="difffile"><h3>How is it different than ZFS/Btrfs snapshots and NTFS Shadow Copy?</h3></a>
 <p>
@@ -167,6 +186,23 @@ SnapRAID creates a filesystem snapshot conceptually similar at other snapshot so
 The difference is that the purpose of SnapRAID is to be able to recover a disk to the saved state
 after a complete disk failure.
 </p>
+<p>
+SnapRAID is more similar at the RAID-Z/RAID functionality of ZFS/Btrfs.
+Compared to them, SnapRAID has the following advantages:
+<ul>
+<li>If the failed disks are too many to allow a recovery, you lose the data only on the failed disks.
+All the data in the other disks is safe.</li>
+<li>You can start with already filled disks.</li>
+<li>You can add disks at any time (not possible with ZFS, but possible with Btrfs).</li>
+<li>It doesn't lock-in your data. You can stop using SnapRAID at any time
+without the need to reformat or move data.</li>
+<li>To access a file, a single disk needs to spin, saving power and
+producing less noise.</li>
+<li>You can have up to six parity levels compared to the three of ZFS RAID-Z and the two of Btrfs RAID-5/6.</li>
+</ul>
+Obviously ZFS/Btrfs have other advantages, like being real-time solutions.
+What is best for you, depends on your specific use case.
+</p>
 
 <a id="diffbak"><h3>How is it different than other backup solutions?</h3></a>
 <p>
@@ -175,15 +211,19 @@ With SnapRAID you need only one additional parity disk to be able to recover the
 Adding more parity disks, you can recover from more disk failures.
 </p>
 <p>
-Note anyway, that only a full backup allows to recover from a complete failure of the disk array and
+Note that only a full backup allows to recover from a complete failure of the disk array and
 it's surely the preferred solution if you can afford it.
-SnapRAID is a good option only if a full backup is not a possible solution.
+SnapRAID is a good option if a full backup is not a possible solution.
 </p>
 
 <a id="adv"><h3>What are the advantages of SnapRAID compared to similar solutions like unRAID/FlexRAID/Windows Storage Spaces?</h3></a>
 <p>
 You can see the <a href="compare.html">Compare</a> page to see it compared to other similar solutions.
-In short, SnapRAID is reliable, OpenSource, multi-platform and free.
+</p>
+<p>
+A strong advantage of SnapRAID is the <span class="bold">integrity and silent error management</span> that is at the same level (if not better)
+of the ZFS and Btrfs filesystems. Instead, unRAID and Storage Space have no integrity check at all!
+FlexRAID is at least able to report silent errors, <a href="http://forum.flexraid.com/index.php/topic,3233.0.html">but not to fix them</a>.
 </p>
 
 <a id="cost"><h3>How much does it cost?</h3></a>

index.html

@@ -67,6 +67,8 @@ recover them.</li>
 <li>You can add disks at any time.</li>
 <li>It doesn't lock-in your data. You can stop using SnapRAID at any
 time without the need to reformat or move data.</li>
+<li>To access a file, a single disk needs to spin, saving power and
+producing less noise.</li>
 </ul>
 </p>