With the attached /etc/raidtab, mkraid /dev/md2 fails incorrectly: [root@toforia root]# mkraid /dev/md2 /dev/md0: array is active -- run raidstop first. mkraid: aborted. (In addition to the above messages, see the syslog and /proc/mdstat as well for potential clues.) [root@toforia root]# In otherwords, attempting to make the /dev/md2 device attempts to access /dev/md0, which is frighteningly wrong.
Created attachment 70984 [details] /etc/raidtab
Just got bitten by the same problem shouldn't for (p = cfg_head; p; p = p->next) { if (strcmp(p->md_name, *args)) continue; if (check_active(cfg)) goto abort; if (force_flag) { fprintf(stderr, "DESTROYING the contents of %s in 5 seconds, Ctrl-C if unsure!\n", *args); become for (p = cfg_head; p; p = p->next) { if (strcmp(p->md_name, *args)) continue; if (check_active(p)) goto abort; if (force_flag) { fprintf(stderr, "DESTROYING the contents of %s in 5 seconds, Ctrl-C if unsure!\n", *args); in mkraid.c ? It seems we're checking if the last of the list is up, every time (got the same problem with md2 here, which was at the end of the list too)
ok, should have checked a little bit further in bugzilla, it's a duplicate of 73365
*** Bug 98609 has been marked as a duplicate of this bug. ***
This looks obviously correct and has been committed to the upstream raidtools sources. The Red Hat raidtools package will have to be updated as well. I've added the fix to the current Red Hat raidtools package. All versions after 1.00.3-6 and later have this fix in it.
The bug is still present in Fedora Core test3, with raidtools-1.00.3-6.
raidtools is gone from FC. This appears to be fixed in RHEL3.