Date: Mon, 28 Aug 2006 09:22:49 -0700 (PDT) From: "R. B. Riddick" <arne_woerner@yahoo.com> To: Pawel Jakub Dawidek <pjd@FreeBSD.org>, Alastair Watts <awatts@pett.com.au> Cc: freebsd-geom@freebsd.org Subject: Re: gvinum behaviour on disk failure Message-ID: <20060828162249.28910.qmail@web30314.mail.mud.yahoo.com> In-Reply-To: <20060828153716.GB64750@garage.freebsd.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
Hmm... I just did some experiments with gnop and my graid5 class: Somehow a gnop device with 100% failure probability is not removed from the graid5, although there were read accesses which failed with EIO... So I added some new lines, that retry up to 50 times (via my good old ENOMEM trick: that is issuing a ENOMEM instead of EIO or so...) and after 10 retries it removes the failing disk... Should we do that for the other geom classes, too? For maximum reliability... Or do I miss something? Or is my graid5 class somehow ill in this point? -Arne __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060828162249.28910.qmail>