summaryrefslogtreecommitdiff
path: root/Documentation/device-mapper
diff options
context:
space:
mode:
authorMikulas Patocka <mpatocka@redhat.com>2017-03-17 19:40:51 +0300
committerMike Snitzer <snitzer@redhat.com>2017-03-24 22:54:23 +0300
commitc2bcb2b702e4684e566d295d687228498184e0c4 (patch)
treed68dcd1dff76ca211a50caac235c36d8f333c8d2 /Documentation/device-mapper
parent1aa0efd4210df1c57764b77040a6615bc9b3ac0f (diff)
downloadlinux-c2bcb2b702e4684e566d295d687228498184e0c4.tar.xz
dm integrity: add recovery mode
In recovery mode, we don't: - replay the journal - check checksums - allow writes to the device This mode can be used as a last resort for data recovery. The motivation for recovery mode is that when there is a single error in the journal, the user should not lose access to the whole device. Signed-off-by: Mikulas Patocka <mpatocka@redhat.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to 'Documentation/device-mapper')
-rw-r--r--Documentation/device-mapper/dm-integrity.txt5
1 files changed, 5 insertions, 0 deletions
diff --git a/Documentation/device-mapper/dm-integrity.txt b/Documentation/device-mapper/dm-integrity.txt
index 2406f56501dc..9d9089f74206 100644
--- a/Documentation/device-mapper/dm-integrity.txt
+++ b/Documentation/device-mapper/dm-integrity.txt
@@ -59,6 +59,11 @@ Target arguments:
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.
+ 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.
5. the number of additional arguments