IMSM for securing reshape process uses special disk area outside metadata
for reshaped area backup purposes. If just reshaped array area requires
backup, bunch of array stripes prepared for reshape is stored in to
Migration Copy Area. In case of reshape interruption, Option ROM during
restart or mdadm during reshape restart (when no reboot occurs) will
restore Migration Copy Area to designation array.
Reshape can be continued form stable array stable state.
The following series implements IMSM checkpointing procedure.
---
Adam Kwolek, Krzysztof Wojcik (22):
imsm: Add migration record to intel_super
Support restore_stripes() from the given buffer
Define dummy functions to mdmon.c
imsm: Add support for copy area and backup operations
imsm: check migration compatibility
FIX: Initialize reshape structure
imsm: Add wait_for_reshape_imsm() implementation
imsm: Implement imsm_manage_reshape(), reshape workhorse
imsm: Check if array degradation has been changed
imsm: Clear migration record when no migration in progress
imsm: Add information about migration record to mdadm '-E' option
imsm: update blocks_per_migr_unit() to support migration record
Add reshape restart support for external metadata
imsm: Implement recover_backup_imsm() for imsm metadata
imsm: Disable checkpoint updating by mdmon for general migration
imsm: Add metadata update type for general migration check-pointing
imsm: Prepare checkpoint update for general migration
imsm: Apply checkpoint metadata update for general migration
FIX: Enable metadata updates for raid0
Do not use backup file for external metadata
imsm: Remove user warning before reshape start
imsm: Unit Tests - remove backup-file during grow command
Assemble.c | 10
Grow.c | 50 +-
mdadm.h | 7
mdmon.c | 23 +
restripe.c | 101 +++-
super-intel.c | 1241 ++++++++++++++++++++++++++++++++++++++++++++--
tests/imsm-grow-template | 5
7 files changed, 1322 insertions(+), 115 deletions(-)
--
Krzysztof Wojcik
--
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
