On Wed, Dec 08, 2004 at 11:52:55AM +0100, Stijn Hoop wrote:
> Scott, your procedure is what I have used, except for:
>
> On Wed, Dec 08, 2004 at 10:09:05AM +0000, Scott Mitchell wrote:
> > 6. Tell vinum to restart the failed subdisk:
> >
> > # vinum start raid.p0.s0
> >
> > 7. Wait ages while the new disk is 'revived'.
> >
> > I was quite impressed that the volume remained available with users
> > accessing it throughout this procedure :-)
>
> Yes I was too -- however I wasn't as impressed with the fact that I had
> parity errors afterwards. Have you run 'vinum checkparity' after these
> rebuilds? In my case I suffered data corruption...
No, but I haven't seen any evidence of corruption in the ~1 year since the
last time I did this, so I guess we got away with it.
> AFAIK the only way to guarantee a consistent rebuild is to do it offline (at
> least in 4.x, haven't tested gvinum in 5.x yet).
>
> > To play it safe you might want to unmount the volume before starting.
>
> I *have* to.
I normally would unmount first if possible, to make the rebuild run faster
if nothing else. Guess I'll make sure to do so in future.
Scott
--
===========================================================================
Scott Mitchell | PGP Key ID | "Eagles may soar, but weasels
Cambridge, England | 0x54B171B9 | don't get sucked into jet engines"
scott at fishballoon.org | 0xAA775B8B | -- Anon
_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
