On 09/04/2017 09:00 PM, NeilBrown wrote: > If a name is given in mdadm.conf and it doesn't match the name in the > metadata, that line will be ignored. If mdadm doesn't find a match in > mdadm.conf and the hostname doesn't match, the the array will be treated > as "foreign" and will be assembled as e.g. /dev/md127 with a symlink > from /dev/md/0_1. > If the name and uuid in mdadm.conf do match the metadata, it will be > treat as "local" and will be given the name that you would expect > (/dev/md0, /dev/md/0). > > So my guess is that the mdadm.conf you had at the time doesn't match > what you have provided above. > > It would be nice to add an option to "mdadm --incremental" to tell it to > update various details like you can with "mdadm --assemble".... I just delete the name and metadata version from mdadm.conf. The above would become: ARRAY /dev/md/0 UUID=d5ea39a9:5ec27c36:c83296d4:70f879d4 ARRAY /dev/md/1 UUID=9bf69b92:2e7ba905:5f959c09:c8fecb99 The default output of mdadm -Es is overspecified for use as mdadm.conf, though it works on precisely the setup that produced it. Phil -- 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
