On Sat, Nov 7, 2009 at 9:06 AM, Doug Ledford [off-list ref] wrote:

quoted

Ok.  That still doesn't address why different commands in mdadm
generate different numbering schemes.

The answer to that is technical implementation details.

<snip>

Ok, that's clear now.

quoted

How do I change the name= spec'n? ...

...

So, if the name=
option is in your mdadm.conf ARRAY line for the array, then changing the
name of the array will require that you do everything I listed above to
update the mdadm.conf file in your mkinitrds and such or else the system
won't boot after you update the name in the superblock.  One last thing,
if this is a / array, then since the only way to update the name is
during assembly, you would have to boot the system from rescue CD and
assemble the array by hand, or else modify the init script in an initrd
image to do the update for you.  Neither of which is a necessarily easy
task if you don't know what you are doing.

Whew.  Messy, but once again clear.

Thanks for the help.

BenDJ
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html