Hello,
I'm testing ISW fake-raid with mdadm 3.3 and I can't add back a disk
to a container previously marked as failed and removed.
Also I'm testing ISW inside a VM so I'm not sure my test case is valid.
So basically my ISW array was created with dmraid. I then installed my
system on this array and rebooted to switch to mdadm. So far so good
everything seems to work perfectly:
# export IMSM_NO_PLATFORM=1
# cat /proc/mdstat
Personalities : [raid1]
md126 : active raid1 sda[1] sdb[0]
2092375 blocks super external:/md127/0 [2/2] [UU]
md127 : inactive sda[1](S) sdb[0](S)
6306 blocks super external:imsm
unused devices: <none>
# mdadm -E /dev/sdb
/dev/sdb:
Magic : Intel Raid ISM Cfg Sig.
Version : 1.1.00
Orig Family : ef92cdd9
[ ... ]
Now I'm marking sda as failed and remove it:
# mdadm --fail /dev/md126 sda
# mdadm --remove /dev/md127 sda
everything works fine until I add back sda to the container:
# mdadm --add /dev/md127 /dev/sda
mdadm: add /dev/sda
# cat /proc/mdstat
Personalities : [raid1]
md126 : active raid1 sdb[0]
2092375 blocks super external:/md127/0 [2/1] [_U]
md127 : inactive sda[1](S) sdb[0](S)
6306 blocks super external:imsm
sda is not added anymore to the array md126 and therefore no resynchro happens.
# mdadm -E /dev/sda
/dev/sda:
MBR Magic : aa55
Partition[0] : 3612577 sectors at 2048 (type 83)
Partition[1] : 560133 sectors at 3616767 (type 05)
Could anybody tell me if that's expected and if so could you englight me ?
Thanks.
--
Francis
--
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
