IMSM doesn't set 'events' field with generation number, so sometimes mdadm tries to re-assembly container using metadata which isn't most recent (e. g. from spare disk). Signed-off-by: Mariusz Dabrowski <mariusz.dabrowski@xxxxxxxxx> --- super-intel.c | 1 + 1 file changed, 1 insertion(+) diff --git a/super-intel.c b/super-intel.c index 0407d43..06b199a 100644 --- a/super-intel.c +++ b/super-intel.c @@ -3381,6 +3381,7 @@ static void getinfo_super_imsm(struct supertype *st, struct mdinfo *info, char * /* do we have the all the insync disks that we expect? */ mpb = super->anchor; + info->events = __le32_to_cpu(mpb->generation_num); for (i = 0; i < mpb->num_raid_devs; i++) { struct imsm_dev *dev = get_imsm_dev(super, i); -- 1.8.3.1 -- 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