On Thu, May 17, 2001 at 10:58:02AM -0600, Chris Jones wrote:
> I have my RAID 5 array working nicely now, but there's a lingering
> quirk.  When I created it, I only had 2 out of 3 components online.
> Then I transferred data onto it and added the third component.  Then I
> did:
> 
> raidctl -a /dev/sd4e raid1
> raidctl -F component2 raid1
> 
> So it added the third component (sd4e) as a spare, and it failed the
> mythical component2 and did a reconstruction onto sd4e.  I also
> rebuilt the parity after this, using raidctl -P.  But now I have this:
> 
> gamera# raidctl -s raid1
> Components:
>            /dev/sd2e: optimal
>            /dev/sd3e: optimal
>           component2: spared
> Spares:
>            /dev/sd4e: used_spare
> 
> 
> How do I get sd4e to be a component, rather than a spare?
> 
> The last time I rebooted, it came up again in degraded mode, with
> component2.  So I had to re-do the reconstruction.

Do you use NetBSD 1.5 ? If so it's a known bug, which has been corrected
since then (parts or the RAIDframe header aren't written to disk).
A raidctl -I should work around the problem.

--
Manuel Bouyer <bouyer@antioche.eu.org>
--