On Monday June 11, [EMAIL PROTECTED] wrote: > > # cat /etc/mdadm/mdadm.conf > DEVICE /dev/sd[a-g]1 > > HOMEHOST ursula > > ARRAY /dev/md1 level=raid5 devices=/dev/sd[defg]1 num-devices=3 > spares=1 spare-group=ubul name=ursula:T2 > UUID=fb8ece28:9a6a31f8:700f37f6:7ee91bcf > ARRAY /dev/md0 level=raid5 devices=/dev/sd[abc]1 num-devices=3 > spare-group=ubul name=ursula:T1 UUID=3e420024:281f9bb1:fd9ef39b:c18153b1
You don't want the "devices=" entries in there. If you leave them there, and sdg1 does get moved to md0, then on the next restart, md0 won't get assembled properly. > > According to the source: > > * If an array has active < raid && spare == 0 && spare_group !=NULL > * Look for another array with spare > 0 and active == raid and same > spare_group > * if found, choose a device and hotremove/hotadd > > This is not happening. What is my mistake? Is "mdadm --monitor" running? That is required to perform spare-migration. NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
