... | ... | @@ -92,7 +92,7 @@ _Available since: 1.3.0 (kernel 4.5)_ |
|
|
Use encoding data from the specified device. This may be the same device where data and hash blocks reside,
|
|
|
in which case fec_start must be outside data and hash areas.
|
|
|
If the encoding data covers additional metadata, it must be accessible on the hash device after the hash blocks.
|
|
|
Note: block sizes for data and hash devices must match. Also, if the verity <dev> is encrypted the <fec_dev> should be too.
|
|
|
Note: block sizes for data and hash devices must match. Also, if the verity <dev> is encrypted the <fec_dev> should be too.
|
|
|
_Available since: 1.3.0 (kernel 4.5)_
|
|
|
|
|
|
* **fec_roots <num>**: Number of generator roots. This equals to the number of parity bytes in the encoding data.
|
... | ... | @@ -100,10 +100,10 @@ For example, in RS(M, N) encoding, the number of roots is M-N. |
|
|
_Available since: 1.3.0 (kernel 4.5)_
|
|
|
|
|
|
* **fec_blocks <num>**: The number of encoding data blocks on the FEC device.
|
|
|
The block size for the FEC device is <data_block_size>.
|
|
|
The block size for the FEC device is <data_block_size>.
|
|
|
_Available since: 1.3.0 (kernel 4.5)_
|
|
|
|
|
|
* **fec_start <offset>**: This is the offset, in <data_block_size> blocks, from the start of the FEC device to the beginning of the encoding data.
|
|
|
* **fec_start <offset>**: This is the offset, in <data_block_size> blocks, from the start of the FEC device to the beginning of the encoding data.
|
|
|
_Available since: 1.3.0 (kernel 4.5)_
|
|
|
|
|
|
_Note: FEC extensions are not yet supported in veritysetup tool._
|
... | ... | |