On Sunday May 20, agaran@xxxxxxxxxxxxx wrote: > > Hello > > > i was trying to build raid 10 from six devices (currently loops but need > to check before i try to do same on physical drives). > > and mdadm gets bit mad, > > mdadm -C -l10 -n6 /dev/loop1 /dev/loop2 /dev/loop3 missing missing > missing > produced weird result What did you expect :-? > mdadm: RUN_ARRAY failed: Input/output error > mdadm: stopped /dev/md0 Yes, lots of mdadm's errors are - like this - quite unhelpful. It is something that I would like to get improved, but it just doesn't get a high priority. > -from dmesg: > md: bind<loop0> > md: bind<loop1> > md: bind<loop2> > md: md0: raid array is not clean -- starting background reconstruction > raid10: not enough operational mirrors for md0 "not enough" means "you don't have the right drives". For every level other than raid10, it doesn't matter which drives you have, it just matter how many there are. For raid10, you do that to have are set of drives that provides all blocks. But I just re-used the error message from raid1. Patches always welcome... 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
