summaryrefslogtreecommitdiff
path: root/mdadm.h
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2013-05-22 12:17:32 +1000
committerNeilBrown <neilb@suse.de>2013-05-22 12:20:39 +1000
commit89ecd3cfe41685cf260ed8f53ff95e2f0ad625cb (patch)
tree728c3e13e277e32f6b69caebc69ab8bb56e6f592 /mdadm.h
parent6b2fc3c162a4a9d6bd332aeddeb4ca9a8ba90ad0 (diff)
Grow: introduce min_offset_change to struct reshape.
raid10 currently uses the 'backup_blocks' field to store something else: a minimum offset change. This is bad practice, we will shortly need to have both for RAID5/6, so make a separate field. Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'mdadm.h')
-rw-r--r--mdadm.h5
1 files changed, 5 insertions, 0 deletions
diff --git a/mdadm.h b/mdadm.h
index 3244c3da..4455b05a 100644
--- a/mdadm.h
+++ b/mdadm.h
@@ -617,6 +617,10 @@ struct metadata_update;
* This will be a multiple of the stripe size in each of the
* 'before' and 'after' geometries.
* If 'blocks' is 0, no restriping is necessary.
+ * 'min_offset_change' is the minimum change to data_offset to
+ * allow the reshape to happen. It is at least the larger of
+ * the old and new chunk sizes, and typically the same as 'blocks'
+ * divided by number of data disks.
*/
struct reshape {
int level;
@@ -626,6 +630,7 @@ struct reshape {
int data_disks;
} before, after;
unsigned long long backup_blocks;
+ unsigned long long min_offset_change;
unsigned long long stripes; /* number of old stripes that comprise 'blocks'*/
unsigned long long new_size; /* New size of array in sectors */
};