On 11/08/2017 04:43 AM, Zhilong Liu wrote: > Hi, Neil and Jes; > I have a question that which name is mdadm expected, md0 or md127 here? > > the case is: > > ./mdadm --quiet -CR /dev/md1 -l1 -n2 /dev/loop0 /dev/loop1 > --homehost=testing --auto=yes > ./mdadm --quiet -CR /dev/md2 -l1 -n2 /dev/loop2 /dev/loop3 > --homehost=testing --auto=yes > ./mdadm --quiet -CR /dev/md0 -l0 -n2 /dev/md1 /dev/md2 > --homehost=testing --auto=yes > > ./mdadm -Ss > ./mdadm --quiet -As -c /dev/null --homehost=testing -vvv > > */linux-apta:~/mdadm-test #/* cat /proc/mdstat > Personalities : [raid1] [raid0] > md127 : active raid0 md1[0] md2[1] > 33792 blocks super 1.2 512k chunks > > md2 : active raid1 loop2[0] loop3[1] > 18944 blocks super 1.2 [2/2] [UU] > > md1 : active raid1 loop0[0] loop1[1] > 18944 blocks super 1.2 [2/2] [UU] > > unused devices: <none> > > And I have another question, I still don't find "when and where" got the > name of md127, > It didn't invoke the find_free_devnm, and I debug with udevadm, still > confused. would > you give me some points on it? I would continue to find which code does > this. Did you pause between mdadm -Ss and mdadm -As ? It may be md0 was still in use. You aren't really guaranteed the name, unless you specify it in /etc/mdadm.conf or on the command line? Cheers, Jes -- 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
