Re: [PATCH] imsm: continue resync on 3-disk RAID10

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

 



On 11/13/2017 06:30 AM, Maksymilian Kunt wrote:
> If RAID10 gets degraded during resync and is stopped, it doesn't continue
> resync after automatic assemble and it is reported to be in sync. Resync
> is blocked because the disk is missing. It should not happen for RAID10 as
> it can still continue with 3 disks.
> 
> Count missing disks. Block resync only if number of missing disks exceeds
> limit for given RAID level (only different for RAID10). Check if the
> disk under recovery is present. If not, resync should be allowed to run.
> 
> Signed-off-by: Maksymilian Kunt <maksymilian.kunt@xxxxxxxxx>
> Signed-off-by: Tomasz Majchrzak <tomasz.majchrzak@xxxxxxxxx>
> ---
>  super-intel.c | 41 +++++++++++++++++++++++++++++++++--------
>  1 file changed, 33 insertions(+), 8 deletions(-)

Applied!

Thanks,
Jes


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