On 09/12/2016 10:03 AM, Yi Zhang wrote: > Hello Artur > With your patch, no "md: export_rdev(sde)" printed after create raid10. > > I found another problem, not sure whether it is reasonable, could you help confirm it, thanks. > When I create one container with 4 disks[1], and create one raid10 with 3 disks(sd[b-d]) + 1 missing [2], but it finally bind the fourth disk: sde [3]. > > [1] mdadm -CR /dev/md0 /dev/sd[b-e] -n4 -e imsm > [2] mdadm -CR /dev/md/Volume0 -l10 -n4 /dev/sd[b-d] missing --size=500M > [3] # cat /proc/mdstat > Personalities : [raid10] > md127 : active raid10 sde[4] sdd[2] sdc[1] sdb[0] > 1024000 blocks super external:/md0/0 128K chunks 2 near-copies [4/4] [UUUU] > > md0 : inactive sde[3](S) sdd[2](S) sdc[1](S) sdb[0](S) > 4420 blocks super external:imsm > > unused devices: <none> I think that this is correct behavior. Because there is a spare disk available in the container, it is used for rebuilding the volume. This is equivalent to: mdadm -CR /dev/md0 /dev/sd[b-d] -n3 -e imsm mdadm -CR /dev/md/Volume0 -l10 -n4 /dev/sd[b-d] missing --size=500M mdadm -a /dev/md0 /dev/sde -- 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
