Description of problem: NB: we don't appear to have an 'mdadm' component, thus the filing under raidtools instead. I had a software raid mirror get out of sync, so the second disk was dropped from the array. Upon trying the following command... # mdadm --manage /dev/md0 -a /dev/hde1 ...nothing happened. This worked though: # mdadm --manage /dev/md0 --add /dev/hde1 Version-Release number of selected component (if applicable): mdadm-2.3.1-3
Problem still present in mdadm 2.5.4-2.fc6...
mdadm also does not support -N (for --name), though on other distros it does.
mdadm shouldn't support the --name option, it's for version 1.0+ superblock raid devices only and by default version 0.90 superblock devices are created. So, unless you manually tell mdadm to create the device with the newer superblock type, there is no place in the superblock to store the name.
I've tracked down the source of the problem regarding usage of the -a versus --add options. A fix will appear in mdadm-2.6.2-2 and later.
mdadm-2.6.2-2.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report.
mdadm-2.6.2-3.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report.
mdadm-2.6.2-4.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report.
mdadm-2.6.2-4.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.