On Wednesday October 18, estair@xxxxxxx wrote: > > FYI, I'm testing 2.6.18.1 and noticed this mis-numbering of RAID10 > members issue is still extant. Even with this fix applied to raid10.c, > I am still seeing repeatable issues with devices assuming a "Number" > greater than that which they had when removed from a running array. That 'Number' change isn't a problem. It is really just an arbitrary label to track a device. Once you fail a device and re-add it, md considers it to be a new device. As long as the 'RaidDevice' number is what you expect, everything is working properly. 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
