mirror of
https://github.com/amadvance/snapraid.git
synced 2026-10-26 10:51:54 -04:00
Adjuts the manpage for six level of parity.
This commit is contained in:
Andrea Mazzoleni
parent
b783e1f745
commit
664337d6f8
3 changed files with 24 additions and 21 deletions
15
snapraid.1
15
snapraid.1
|
|
@ -62,13 +62,14 @@ features of SnapRAID are:
|
|||
All your data is hashed to ensure data integrity and to avoid
|
||||
silent corruption.
|
||||
.IP \(bu
|
||||
If more than two disks fail, you lose the data only on the
|
||||
failed disks. All the data in the other disks is safe.
|
||||
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.
|
||||
.IP \(bu
|
||||
If you accidentally delete some files in a disk, you can
|
||||
recover them.
|
||||
.IP \(bu
|
||||
You can start using SnapRAID with already filled disks.
|
||||
You can start with already filled disks.
|
||||
.IP \(bu
|
||||
The disks can have different sizes.
|
||||
.IP \(bu
|
||||
|
|
@ -116,7 +117,7 @@ With RAID you get a speed boost with striping.
|
|||
It doesn\(cqt support real\(hytime recovery.
|
||||
With RAID you do not have to stop working when a disk fails.
|
||||
.IP \(bu
|
||||
It\(cqs able to recover damages only from up to two disks.
|
||||
It\(cqs able to recover damages only from a limited number of disks.
|
||||
With a Backup you are able to recover from a complete
|
||||
failure of the whole disk array.
|
||||
.IP \(bu
|
||||
|
|
@ -713,15 +714,15 @@ it stops proceeding unless you specify this option.
|
|||
This allows to detect when your disks are mounted in the
|
||||
wrong mount points.
|
||||
It\(cqs anyway allowed to have a single UUID change with
|
||||
single parity, and two with double parity, because it\(cqs
|
||||
the normal case of replacing disks.
|
||||
single parity, and more with multiple parity, because it\(cqs
|
||||
the normal case of replacing disks after a recover.
|
||||
This option can be used only with the \(a"sync\(a", \(a"check\(a" or
|
||||
\(a"fix\(a" command.
|
||||
.TP
|
||||
.B \(hyD, \(hy\(hyforce\(hydevice
|
||||
Forces the insecure operation of fixing with disks on the same
|
||||
physical device.
|
||||
If SnapRAID detects that two disks have the same device ID,
|
||||
If SnapRAID detects that some disks have the same device ID,
|
||||
it stops proceeding, because it\(cqs not a supported configuration.
|
||||
But it could happen that you want to temporarely restore a lost
|
||||
disk in the free space left in an already used disk. and this
|
||||
|
|
|
|||
15
snapraid.d
15
snapraid.d
|
|
@ -28,11 +28,12 @@ Description
|
|||
|
||||
* All your data is hashed to ensure data integrity and to avoid
|
||||
silent corruption.
|
||||
* If more than two disks fail, you lose the data only on the
|
||||
failed disks. All the data in the other disks is safe.
|
||||
* 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.
|
||||
* If you accidentally delete some files in a disk, you can
|
||||
recover them.
|
||||
* You can start using SnapRAID with already filled disks.
|
||||
* 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
|
||||
|
|
@ -68,7 +69,7 @@ Limitations
|
|||
With RAID you get a speed boost with striping.
|
||||
* It doesn't support real-time recovery.
|
||||
With RAID you do not have to stop working when a disk fails.
|
||||
* It's able to recover damages only from up to two disks.
|
||||
* It's able to recover damages only from a limited number of disks.
|
||||
With a Backup you are able to recover from a complete
|
||||
failure of the whole disk array.
|
||||
* Only file, timestamps, symlinks and hardlinks are saved.
|
||||
|
|
@ -508,15 +509,15 @@ Options
|
|||
This allows to detect when your disks are mounted in the
|
||||
wrong mount points.
|
||||
It's anyway allowed to have a single UUID change with
|
||||
single parity, and two with double parity, because it's
|
||||
the normal case of replacing disks.
|
||||
single parity, and more with multiple parity, because it's
|
||||
the normal case of replacing disks after a recover.
|
||||
This option can be used only with the "sync", "check" or
|
||||
"fix" command.
|
||||
|
||||
-D, --force-device
|
||||
Forces the insecure operation of fixing with disks on the same
|
||||
physical device.
|
||||
If SnapRAID detects that two disks have the same device ID,
|
||||
If SnapRAID detects that some disks have the same device ID,
|
||||
it stops proceeding, because it's not a supported configuration.
|
||||
But it could happen that you want to temporarely restore a lost
|
||||
disk in the free space left in an already used disk. and this
|
||||
|
|
|
|||
15
snapraid.txt
15
snapraid.txt
|
|
@ -35,11 +35,12 @@ features of SnapRAID are:
|
|||
|
||||
* All your data is hashed to ensure data integrity and to avoid
|
||||
silent corruption.
|
||||
* If more than two disks fail, you lose the data only on the
|
||||
failed disks. All the data in the other disks is safe.
|
||||
* 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.
|
||||
* If you accidentally delete some files in a disk, you can
|
||||
recover them.
|
||||
* You can start using SnapRAID with already filled disks.
|
||||
* 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
|
||||
|
|
@ -78,7 +79,7 @@ Other limitations are:
|
|||
With RAID you get a speed boost with striping.
|
||||
* It doesn't support real-time recovery.
|
||||
With RAID you do not have to stop working when a disk fails.
|
||||
* It's able to recover damages only from up to two disks.
|
||||
* It's able to recover damages only from a limited number of disks.
|
||||
With a Backup you are able to recover from a complete
|
||||
failure of the whole disk array.
|
||||
* Only file, timestamps, symlinks and hardlinks are saved.
|
||||
|
|
@ -555,15 +556,15 @@ SnapRAID provides the following options:
|
|||
This allows to detect when your disks are mounted in the
|
||||
wrong mount points.
|
||||
It's anyway allowed to have a single UUID change with
|
||||
single parity, and two with double parity, because it's
|
||||
the normal case of replacing disks.
|
||||
single parity, and more with multiple parity, because it's
|
||||
the normal case of replacing disks after a recover.
|
||||
This option can be used only with the "sync", "check" or
|
||||
"fix" command.
|
||||
|
||||
-D, --force-device
|
||||
Forces the insecure operation of fixing with disks on the same
|
||||
physical device.
|
||||
If SnapRAID detects that two disks have the same device ID,
|
||||
If SnapRAID detects that some disks have the same device ID,
|
||||
it stops proceeding, because it's not a supported configuration.
|
||||
But it could happen that you want to temporarely restore a lost
|
||||
disk in the free space left in an already used disk. and this
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue