The following series adds possibility to reshape all (raid0/5) arrays in container for expansion feature. The main problem resolved in this series is how initialize second (and next) raid0 reshapes for container reshape executed as set of array reshapes. For i.e. second raid0 array mdmon should initialize metadata to let know to mdadm that there is something more to reshape. But problem is what to do when mdmon is not loaded? (for first raid0 array this is not a problem, reshape_super() in mdadm updates metadata). this is resolved by allowing mdadm to know what was reshaped so far. This allows to reshape arrays that are not reshaped yet, without update from mdmon. BR Adam --- Adam Kwolek (6): FIX: sync_completed == 0 causes reshape cancellation in metadata FIX: mdadm hangs during reshape FIX: mdadm throws coredump on exit in error case FIX: reshape raid0 on second array FIX: continue raid0 reshape imsm: Update metadata for second array Grow.c | 95 +++++++++++++++++++++++++++++++++++++++++++++++++++------ monitor.c | 4 ++ super-intel.c | 35 +++++++++++++++++++-- 3 files changed, 120 insertions(+), 14 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