On 12/07/2017 04:23 AM, Tomasz Majchrzak wrote:
> If disk has disappeared from the system and appears again, it is added to the
> corresponding container as long the metadata matches and disk number is set.
> This code had no effect on imsm until commit 20dc76d15b40 ("imsm: Set disk slot
> number"). Now the disk is added to container but not to the array - it is
> correct as the disk is out-of-sync. Rebuild should start for the disk but it
> doesn't. There is the same behaviour for both imsm and ddf metadata.
>
> There is no point to handle out-of-sync disk as "good member of array" so
> remove that part of code. There are no scenarios when monitor is already
> running and disk can be safely added to the array. Just write initial metadata
> to the disk so it's taken for rebuild.
>
> Signed-off-by: Tomasz Majchrzak <tomasz.majchrzak@xxxxxxxxx>
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
