This series corrects problems occurred during restart multi arrays reshape:
1. Assembled incrementally array during reshape is assembled degraded
2. Reshape cannot be continued after reboot. '--continue' gives an error
3. When raid0 arrays are reshaped, first array is reshaped only
4. Size doesn't change on second raid0 array
Please note that patch 'imsm: FIX: No new missing disks are allowed during general migration' can be easily extended by:
- Narrow it to incremental assembly only
- Array can be pushed to be assembled by using e.g. 'force' option during incremental assembly.
Other issue addressed in this series is chunk size change from 128k to 4k problem.
BR
Adam
---
Adam Kwolek (12):
FIX: Do not try to (continue) reshape using inactive array
FIX: restart reshape when reshape process is stopped just between 2 reshapes
imsm: FIX: Clear migration record when migration switches to next volume.
imsm: FIX: use md position to reshape restart
FIX: use md position to reshape restart
imsm: FIX: Chunk size migration problem
Flush mdmon before next reshape step during container operation
Fix: Sometimes mdmon throws core dump during reshape
imsm: FIX: imsm_get_allowed_degradation() doesn't count degradation for raid1
FIX: Array is not run when expansion disks are added
imsm: FIX: No new missing disks are allowed during general migration
FIX: NULL pointer to strdup() can be passed
Assemble.c | 2 -
Grow.c | 124 ++++++++++++++++++++++++++++++++++++++++++++-------------
managemon.c | 6 +++
msg.c | 10 +++++
msg.h | 1
super-intel.c | 47 +++++++++++++++++++---
util.c | 5 +-
7 files changed, 159 insertions(+), 36 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
