[PATCH] imsm: FIX: Migration Raid0->Raid5 cannot be restarted correctly

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



When array raid0 is migrated to raid5, reshape cannot be continued
correctly due to wrong array parameters settings.
Raid disks number is set too big.

There is no need, during raid0->raid5 migration to increase
info->array.raid_disks, it is already set to final value using
designation map information.

Signed-off-by: Adam Kwolek <adam.kwolek@xxxxxxxxx>
---

 super-intel.c |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/super-intel.c b/super-intel.c
index 075385a..40fd940 100644
--- a/super-intel.c
+++ b/super-intel.c
@@ -2133,7 +2133,6 @@ static void getinfo_super_imsm_volume(struct supertype *st, struct mdinfo *info,
 				/* conversion is happening as RAID5 */
 				info->array.level = 5;
 				info->array.layout = ALGORITHM_PARITY_N;
-				info->array.raid_disks += 1;
 				info->delta_disks -= 1;
 				break;
 			default:

--
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


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux