Has anybody EVER successfully recovered VINUM?

[Stijn Hoop]

On Wed, Dec 08, 2004 at 11:30:13AM +0000, Scott Mitchell wrote:
> On Wed, Dec 08, 2004 at 11:52:55AM +0100, Stijn Hoop wrote:
> > > 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.

Well I'm still not sure whether this was something hardware related as the box
is still fishy. However, in the ~5 times that I did an offline rebuild I've
never encountered parity errors as opposed to the ~3 times of online rebuilds
that definitely screwed up the parity. In addition, the author of vinum
couldn't assert that 4.x vinum supported online rebuilds (not a complaint,
just a fact), so I'm not rebuilding online anymore.

> > 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.

I'm just saying that in my case it didn't work out well. As with any other
advice, it might just work for you :)

--Stijn

-- 
"A mouse is a device used to point at the xterm you want to type in."
		-- Kim Alm, alt.sysadmin.recovery
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20041208/e4b71671/attachment.bin