Subject: Re: raidframe copyback blocks the whole system !?
To: None <email@example.com>
From: Greg Oster <firstname.lastname@example.org>
Date: 06/25/2002 10:28:01
Markus W Kilbinger writes:
> >>>>> "Greg" == Greg Oster <email@example.com> writes:
> Greg> Well... if you have hot-swap drives, then you could just
> Greg> stuff the new drive in place of the old one, and not worry
> Greg> about doing a copyback.. (i.e. the new drive you put in
> Greg> becomes the hot spare).
> Hmm, how to come!? The old/new drive still has state 'failed', the
> spare is 'used_spare'. So, what will happen if another drive fails in
> this stage?
You stuff another drive into the box, hot-add it, and rebuild to it :)
> How will the 'failed' drive become the new spare _without_ reboot?
You stuff a fresh drive into that slot, and when a different drive fails,
rebuild to the fresh drive. Not quite the same as a spare, but works much
the same. :)
> Greg> If you don't have hot-swap drives, then you'll have to take
> Greg> things off-line anyway, and at that point you can just
> Greg> shuffle the disks around :)
> Yeah, but that's what I want to avoid in my (academic) scenario... ;-)
> -> send-pr?
> Greg> If you'd like. There may already be a PR, but I don't recall
> Greg> for sure.. I do know that this issue is on my RAIDframe
> Greg> "todo" list..
> Ok, that's sufficient! ;-)