Re: RaidFrame Raid-1 problem (can't ditch a failing disk)

[Greg Oster <oster%cs.usask.ca@localhost>]

On Mon, 1 Mar 2010 12:51:10 +0100
Tobias Nygren <tnn%NetBSD.org@localhost> wrote:

> On Sun, 28 Feb 2010 10:33:01 -0600
> Greg Oster <oster%cs.usask.ca@localhost> wrote:
> 
> > The issue is that the rf_parity_map.c bits arn't checking to see if a
> > component is valid before attempting to get (and then use!) a component
> > label.  I'll see if I can whip up a patch for you to test, if Jed
> > doesn't beat me to it...  (I missed this issue when I was looking over
> > the paritymap stuff... :( )
> > 
> > This will also be a critical patch to get pulled up for NetBSD 5.1 as
> > well...
> > 
> > Later...
> > 
> > Greg Oster
> 
> Not sure if it's the same problem, but I recently had raidframe crash
> with a similar backtrace when attempting to configure a new raid mirror
> (with -C) with one component marked as absent.

Yup.. it's more-or-less the same issue...

> There does not currently seem to be any way to disable or tweak the
> parity map when configuring a new raid set. It would be nice if the -M
> option could be used together with -C (or -c).
> 
> -Tobias


Later...

Greg Oster