diff options
author | Heinz Mauelshagen <heinzm@redhat.com> | 2016-11-29 19:26:08 +0100 |
---|---|---|
committer | Mike Snitzer <snitzer@redhat.com> | 2016-12-08 14:13:13 -0500 |
commit | 58fc4fedee4a6e6e42f01da6ebaa0de0088fc8e3 (patch) | |
tree | df81bac07e45ee8fe72b356235d24e4b67e8cde1 /Documentation/device-mapper | |
parent | 11e2968478edc07a75ee1efb45011b3033c621c2 (diff) | |
download | linux-58fc4fedee4a6e6e42f01da6ebaa0de0088fc8e3.tar.bz2 |
Documentation: dm raid: define data_offset status field
Signed-off-by: Heinz Mauelshagen <heinzm@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to 'Documentation/device-mapper')
-rw-r--r-- | Documentation/device-mapper/dm-raid.txt | 4 |
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: in RAID1/10 or wrong parity values found in RAID4/5/6. This value is valid only after a "check" of the array is performed. A healthy array has a 'mismatch_cnt' of 0. + <data_offset> The current data offset to the start of the user data on + each component device of a raid set (see the respective + raid parameter to support out-of-place reshaping). + Message Interface ----------------- |