Subject: Re: Reconfiguring RAIDframe components (was Re: hot spares for RAID 1 sets?)
To: Todd Vierling <firstname.lastname@example.org>
From: Greg Oster <email@example.com>
Date: 08/16/2005 09:25:18
Todd Vierling writes:
> On Tue, 16 Aug 2005, Greg Oster wrote:
> > > Is it possible
> > > to reconfigure easily to make /dev/wd1h the non-"spare" column-1 disk her
> > > if only to make the set look more sane?
> > Not at this time. It's one of the things on my TODO list, but the
> > "right fix" requires gutting how components and spares are handled,
> > and that's a bit of a major undertaking... A reboot will typically
> > fix the cosmetic issue, and so it's never become a priority...
> Well, this set is configured -A root, so a reboot doesn't fix it as-is.
Hmm... it sure should... At least, I'm sure that functionality was
there in 2.0... (it's certainly there for 3.0)
> But does that mean that if I dump its config file, turn off -A root, boot
> into an install disk, then reconfigure with a (fixed) config file, it should
> go back to "normal"?
If the set gets shutdown properly, then the spare disk should show up
in the right spot when the system comes back up... I know there were
a few minor bugs related to that, but they should have been fixed for
2.0 (IIRC). You may also be able to cheat your way around those bugs by
doing another "raidctl -I" on the set before rebooting -- that should at
least force the labels to be close enough that after a reboot, the
used_spare should show up in the regular component spot (though depending
on the bug, it may be marked as failed or something).