Date: Mon, 28 Aug 2006 08:54:14 -0500 From: Eric Anderson <anderson@centtech.com> To: Alastair Watts <awatts@pett.com.au> Cc: "R. B. Riddick" <arne_woerner@yahoo.com>, freebsd-geom@freebsd.org Subject: Re: gvinum behaviour on disk failure Message-ID: <44F2F586.6060600@centtech.com> In-Reply-To: <44F2F3C5.7090001@pett.com.au> References: <20060828132846.81472.qmail@web30308.mail.mud.yahoo.com> <44F2F3C5.7090001@pett.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/28/06 08:46, Alastair Watts wrote: > R. B. Riddick wrote: [..snip..] >>> Yes... I noticed gvinum was very different to Greg's original vinum >>> suite ;) But this seems to be a fundamental thing that's missing from >>> gvinum - the ability to recover from a drive failure and to be able to >>> service the request from a different plex. >> Hmm... Does gmirror overcome these drawbacks? > > Don't know. If it doesn't then it's still a problem in my opinion :) We > have more machines using gmirror than gvinum (only 1 with gvinum), but > so far only the machine with gvinum has had a drive fail since FBSD 5.3 > upwards. I've had a drive that belonged to a mirrored die before, and didn't notice it until I logged in to the machine and poked around, so it did do its job. I've also had a drive in a gmirror go bad, and it hung the whole box, but that isn't gmirrors' fault as far as I know. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44F2F586.6060600>