Description of Problem:

mkraid complains that the device is busy

Version-Release number of selected component (if applicable):
1.00.2 (tested both on RH 7.3 and the "null" public beta)

How Reproducible:

Create a new entry for (say) /dev/md4 in /etc/raidtab, but do not enter it
as a last entry (let's say the last is for /dev/md3, and add the one for
/dev/md4 at the beginning of raidtab). Activate the /dev/md3 using raidstart
provided it is not active yet.

Now try to run mkraid /dev/md4. You got the error message saying that "/dev/md3
is active" (note that it complains about md3, not md4).

The bug is in mkraid.c around the line 247: it tries to walk the list of
all config entries (the actual one being in the variable "p"), but then
checks the state using the unrelated variable called "cfg", which incidentally
points to the last entry in /etc/raidtab. So if the last entry is active,
mkraid fails. What is worse - if the last entry is not active, it can allow
to overwrite the existing array even though it is in use!

Patch is as follows (cut&paste, so tabs are mangled):

--- raidtools-1.00.2/mkraid.c.orig	2002-04-15 10:09:11.000000000 +0200
+++ raidtools-1.00.2/mkraid.c	2002-09-03 17:22:04.000000000 +0200
@@ -244,7 +244,7 @@
     while (*args) {
 	for (p = cfg_head; p; p = p->next) {
 	    if (strcmp(p->md_name, *args)) continue;
-
    if (check_active(cfg)) 
+
    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);