Neil Brown <[EMAIL PROTECTED]> wrote:
> The problem is that you are using both MD_BOOT and AUTODETECT to start
> the raid arrays, and the code isn't coping.
> With 2.4.0, you have a choice for configuring raid at boot time. You
> can use autodetect by setting partition types, or use md= arguments to
> the kernel. You can even use both for different arrays, but not both
> for the same array.
> For following patch should make it cope better if you try to do both.
The patch worked fine on test8-pre1. Thanks. It seems that test4 did
not autodetect the raids, so the problem did not manifest itself.
Anyway, I'm getting the idea that running RAID (for reliability) and a
bleeding edge kernel (unstable) is not a very, er.... good idea. I
guess I'll go back to the 2.2 series and try the backport.
Thanks
Stephen
> --- md.c 2000/08/31 23:07:29 1.1
> +++ md.c 2000/08/31 23:08:57
> @@ -3745,6 +3745,10 @@
> if (!(md_setup_args.set & (1 << minor)))
> continue;
> printk("md: Loading md%d.\n", minor);
> + if (mddev_map[minor].mddev) {
> + printk(".. md%d already autodetected - use
>raid=noautodetect\n");
> + continue;
> + }
> mddev = alloc_mddev(MKDEV(MD_MAJOR,minor));
> if (md_setup_args.pers[minor]) {
> /* non-persistent */
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
