diff options
| author | NeilBrown <neilb@suse.de> | 2012-05-21 09:27:00 +1000 |
|---|---|---|
| committer | NeilBrown <neilb@suse.de> | 2012-05-21 09:27:00 +1000 |
| commit | 2c810cddc44d6f95cef75df3f07fc0850ff92417 (patch) | |
| tree | 185b35ce06656a53327dd66343f0926aa5a910d7 /drivers/md/md.h | |
| parent | b5e1b8cee7ad58a15d2fa79bcd7946acb592602d (diff) | |
| download | linux-2c810cddc44d6f95cef75df3f07fc0850ff92417.tar.gz linux-2c810cddc44d6f95cef75df3f07fc0850ff92417.tar.bz2 linux-2c810cddc44d6f95cef75df3f07fc0850ff92417.zip | |
md: allow a reshape operation to be reversed.
Currently a reshape operation always progresses from the start
of the array to the end unless the number of devices is being
reduced, in which case it progressed in the opposite direction.
To reverse a partial reshape which changes the number of devices
you can stop the array and re-assemble with the raid-disks numbers
reversed and it will undo.
However for a reshape that does not change the number of devices
it is not possible to reverse the reshape in the middle - you have to
wait until it completes.
So add a 'reshape_direction' attribute with is either 'forwards' or
'backwards' and can be explicitly set when delta_disks is zero.
This will become more important when we allow the data_offset to
change in a reshape. Then the explicit statement of what direction is
being used will be more useful.
This can be enabled in raid5 trivially as it already supports
reverse reshape and just needs to use a different trigger to request it.
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md/md.h')
| -rw-r--r-- | drivers/md/md.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/md/md.h b/drivers/md/md.h index 1c2063ccf48e..d51c0ca37777 100644 --- a/drivers/md/md.h +++ b/drivers/md/md.h @@ -262,6 +262,7 @@ struct mddev { sector_t reshape_position; int delta_disks, new_level, new_layout; int new_chunk_sectors; + int reshape_backwards; atomic_t plug_cnt; /* If device is expecting * more bios soon. |