On Thursday January 10, jed@xxxxxxxxxxxxx wrote: > > It looks to me like md inspects and attempts to assemble after each > drive controller is scanned (from dmesg, there appears to be a failed > bind on the first three devices after they are scanned, and then again > when the second controller is scanned). Would the scan order cause a > spare to be swapped in? > This suggests that "mdadm --incremental" is being used to assemble the arrays. Every time udev finds a new device, it gets added to whichever array is should be in. If it is called as "mdadm --incremental --run", then it will get started as soon as possible, even if it is degraded. With the "--run", it will wait until all devices are available. Even with "mdadm --incremental --run", you shouldn't get a resync if the last device is added before the array is written to. What distro are you running? What does grep -R mdadm /etc/udev show? NeilBrown - 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
