mirror of
https://github.com/amadvance/snapraid.git
synced 2026-10-26 02:49:02 -04:00
Fix typo in man
This commit is contained in:
parent
b424a503a0
commit
935d7cd09f
3 changed files with 3 additions and 3 deletions
|
|
@ -1363,7 +1363,7 @@ WARNING! This option is for experts only, and it\'s highly
|
|||
recommended to not change it. To change again this value in
|
||||
future you\'ll have to recreate the whole parity!
|
||||
.PP
|
||||
A reason to use a different hashsize is if you have a lot of small
|
||||
A reason to use a different blocksize is if you have a lot of small
|
||||
files. In the order of many millions.
|
||||
.PP
|
||||
For each file, even of few bytes, a whole block of parity is allocated,
|
||||
|
|
|
|||
|
|
@ -1062,7 +1062,7 @@ Configuration
|
|||
recommended to not change it. To change again this value in
|
||||
future you'll have to recreate the whole parity!
|
||||
|
||||
A reason to use a different hashsize is if you have a lot of small
|
||||
A reason to use a different blocksize is if you have a lot of small
|
||||
files. In the order of many millions.
|
||||
|
||||
For each file, even of few bytes, a whole block of parity is allocated,
|
||||
|
|
|
|||
|
|
@ -1138,7 +1138,7 @@ WARNING! This option is for experts only, and it's highly
|
|||
recommended to not change it. To change again this value in
|
||||
future you'll have to recreate the whole parity!
|
||||
|
||||
A reason to use a different hashsize is if you have a lot of small
|
||||
A reason to use a different blocksize is if you have a lot of small
|
||||
files. In the order of many millions.
|
||||
|
||||
For each file, even of few bytes, a whole block of parity is allocated,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue