Thanks for the Patch, Klaudius
I will try it today evening and look how it works.
Did you supply it to Ingo for suggestion or is he aware of this bug?
bye
Ulf
> I had the same problem and found the reason in the read-balancing code,
> which doesn't recognize, that a disk had been set faulty. So it tries to
> read
> from a logically unavailable disk and the read access to device [00:00]
> generates the Oops.
>
> With this small patch I could solve it on my machine:
>
> --- drivers/block/raid1.c.orig Thu Sep 7 18:20:46 2000
> +++ drivers/block/raid1.c Thu Sep 7 18:26:14 2000
> @@ -367,8 +367,11 @@
> int i;
>
> for (i = 0; i < disks; i++)
> - if (conf->mirrors[i].next == target)
> + if (conf->mirrors[i].next == target) {
> conf->mirrors[i].next =
> conf->mirrors[target].next;
> + if (conf->last_used == target)
> + conf->last_used = i;
> + }
> }
>
> #define LAST_DISK KERN_ALERT \
>
>
>
> Klaudius
--
Ulf Dambacher
Tel.: +49 721 38 42 550
eMail: [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
