Hi, Here is my observation: Imagine that we have an array that went degraded leaving a cookie (appropriate config is there). When we plug in a disk without metadata into the same slot that was used by this array mdadm should add the new disk to that array. This is the way it goes at the moment. What should happen when we connect a disk with spare metadata to this slot? At the moment it is added to the original array or (imsm) anywhere. Wouldn't it be reasonable to use the slot information when we have a spare? In some cases Monitor will move it anyway but there is a chance that another array may get it before the "owner" of this slot. Or that Monitor may not move it as domain of the array doesn't include domain of this slot any more. We agreed that domain shouldn't be checked when there is a cookie but this only applies to Incremental. (It will be implemented shortly.) "spare-same-slot" sounds to me like a spare in the same slot should also go to the array described by cookie. What is your opinion? Anna -- 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
