aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorHeinz Mauelshagen <heinzm@redhat.com>2016-11-29 13:26:08 -0500
committerMike Snitzer <snitzer@redhat.com>2016-12-08 14:13:13 -0500
commit58fc4fedee4a6e6e42f01da6ebaa0de0088fc8e3 (patch)
treedf81bac07e45ee8fe72b356235d24e4b67e8cde1
parent11e2968478edc07a75ee1efb45011b3033c621c2 (diff)
Documentation: dm raid: define data_offset status field
Signed-off-by: Heinz Mauelshagen <heinzm@redhat.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com>
-rw-r--r--Documentation/device-mapper/dm-raid.txt4
1 files changed, 4 insertions, 0 deletions
diff --git a/Documentation/device-mapper/dm-raid.txt b/Documentation/device-mapper/dm-raid.txt
index 9bd531aa2279..5e3786fd9ea7 100644
--- a/Documentation/device-mapper/dm-raid.txt
+++ b/Documentation/device-mapper/dm-raid.txt
@@ -242,6 +242,10 @@ recovery. Here is a fuller description of the individual fields:
242 in RAID1/10 or wrong parity values found in RAID4/5/6. 242 in RAID1/10 or wrong parity values found in RAID4/5/6.
243 This value is valid only after a "check" of the array 243 This value is valid only after a "check" of the array
244 is performed. A healthy array has a 'mismatch_cnt' of 0. 244 is performed. A healthy array has a 'mismatch_cnt' of 0.
245 <data_offset> The current data offset to the start of the user data on
246 each component device of a raid set (see the respective
247 raid parameter to support out-of-place reshaping).
248
245 249
246Message Interface 250Message Interface
247----------------- 251-----------------