... | ... | @@ -61,10 +61,11 @@ If some extension was added later, it is mentioned in the description. |
|
|
**J** - journaled writes - data and integrity tags are written to the journal and atomicity is guaranteed.
|
|
|
In case of crash, either both data and tag or none of them are written. The journaled mode degrades write
|
|
|
throughput twice because the data have to be written twice.
|
|
|
**B** - bitmap mode - data and metadata are written without any synchronization, the driver maintains
|
|
|
a bitmap of dirty regions where data and metadata don't match.
|
|
|
**B** - bitmap mode
|
|
|
_Available since: 1.3.0 (kernel 5.2)_
|
|
|
Data and metadata are written without any synchronization, the driver maintains
|
|
|
a bitmap of dirty regions where data and metadata don't match.
|
|
|
This mode can only be used with internal hash.
|
|
|
_Available since: 1.3.0 (kernel 5.2)_
|
|
|
**R** - recovery mode - in this mode, journal is not replayed, checksums are not checked and writes
|
|
|
to the device are not allowed. This mode is useful for data recovery if the device cannot be activated in any
|
|
|
of the other standard modes.
|
... | ... | @@ -125,12 +126,12 @@ _Available since: 1.2.0 (kernel 4.19)_ |
|
|
|
|
|
* **sectors_per_bit**: number
|
|
|
In the bitmap mode, this parameter specifies the number of 512-byte sectors that corresponds
|
|
|
to one bitmap bit.
|
|
|
to one bitmap bit.
|
|
|
_Available since: 1.3.0 (kernel 5.2)_
|
|
|
|
|
|
* **bitmap_flush_interval**: number
|
|
|
The bitmap flush interval in milliseconds.
|
|
|
The metadata buffers are synchronized when this interval expires.
|
|
|
The bitmap flush interval in milliseconds.
|
|
|
The metadata buffers are synchronized when this interval expires.
|
|
|
_Available since: 1.3.0 (kernel 5.2)_
|
|
|
|
|
|
### Optional Journal encryption parameters
|
... | ... | |