Currently reshaped/expanded array is assembled but it stays in inactive state.
This patches allows for array assembly when array is under expansion.
Array with reshape/expansion information in metadata is assembled
and reshape process continues automatically.
Next step:
Problem is how to address container operation during assembly.
1. After first array being reshaped, assebly process looks if mdmon
sets migration for other array in container. If yes it continues work
for next array.
2. Assembly process performs reshape of currently reshaped array only.
Mdmon sets next array for reshape and user triggers manually mdadm
to finish container operation with just the same parameters set.
Reshape finish can be executed for container operation by container re-assembly
also (this works in current code).
BR
Adam
---
Adam Kwolek (3):
FIX: Assemble device in reshape state with new disks number
imsm: FIX: Report correct array size during reshape
imsm: FIX: initalize reshape progress as it is stored in metatdata
Assemble.c | 2 ++
super-intel.c | 24 +++++++++++++++++++++++-
2 files changed, 25 insertions(+), 1 deletions(-)
--
Signature
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
