From: Neil Brown <neilb@cse.unsw.edu.au>
To: Robert Murray <rob@mur.org.uk>
Date: Tue, 30 Nov 2004 12:58:43 +1100
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16811.54227.681707.243145@cse.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: raid1 oops in 2.6.9 (debian package 2.6.9-1-686-smp)
In-Reply-To: message from Robert Murray on Sunday November 28
References: <20041128142840.GA4119@mur.org.uk>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1055
Lines: 27

On Sunday November 28, rob@mur.org.uk wrote:
> Hi
> 
> The complete console log can be found at
> http://haylott.plus.com/~robbie/md-oops.txt

This looks like a known bug that is fixed in current 2.6.10
pre-releases. 
> 
> hde is a failed drive. In this log, hdg (the other drive in the raid1
> array) is not present. This oops also occurs when hdg is present. I
> don't know why it tries to use hde when it has been failed for some
> time now.

It tries to use hde because it sees no reason not to.
When a drive fails, md never writes to it again, so the record of it
being part of a raid1 array is still there.
If it is assembled with another drive that "knows" that hde has
failed, then it won't accept hde into the array.  But the hdg missing,
hde is the best bet it has, and it tries it anyway.

NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/