mirror of
https://github.com/amadvance/snapraid.git
synced 2026-10-26 19:01:57 -04:00
Update HISTORY
This commit is contained in:
parent
9a21995a61
commit
28f66faa1f
2 changed files with 5 additions and 4 deletions
4
HISTORY
4
HISTORY
|
|
@ -1,8 +1,8 @@
|
|||
SnapRAID HISTORY
|
||||
================
|
||||
|
||||
11.4 2019/05
|
||||
============
|
||||
11.4 2019/06 (WorkInProgress)
|
||||
=============================
|
||||
* In fixing, if a parity is filtered out, don't attempt to recover its size,
|
||||
and proceed without it if missing.
|
||||
* Avoid unnecessary parity read when fixing the parity itself.
|
||||
|
|
|
|||
|
|
@ -38,6 +38,8 @@ big files that rarely change.
|
|||
Beside the ability to recover from disk failures, other
|
||||
features of SnapRAID are:
|
||||
|
||||
* You can use disk already filled with files, without the need to
|
||||
reformat them. You will access them like now.
|
||||
* All your data is hashed to ensure data integrity and to avoid
|
||||
silent corruption.
|
||||
* If the failed disks are too many to allow a recovery,
|
||||
|
|
@ -45,12 +47,11 @@ features of SnapRAID are:
|
|||
All the data in the other disks is safe.
|
||||
* If you accidentally delete some files in a disk, you can
|
||||
recover them.
|
||||
* You can start with already filled disks.
|
||||
* The disks can have different sizes.
|
||||
* You can add disks at any time.
|
||||
* It doesn't lock-in your data. You can stop using SnapRAID at any
|
||||
time without the need to reformat or move data.
|
||||
* To access a file, a single disk needs to spin, saving power and
|
||||
* To access a file, only a single disk needs to spin, saving power and
|
||||
producing less noise.
|
||||
|
||||
The official site of SnapRAID is:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue