From owner-freebsd-stable@FreeBSD.ORG Sat Dec 18 23:15:22 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 074D816A4CE for ; Sat, 18 Dec 2004 23:15:22 +0000 (GMT) Received: from havoc.eusc.inter.net (havoc.eusc.inter.net [213.73.101.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8EB143D2D for ; Sat, 18 Dec 2004 23:15:21 +0000 (GMT) (envelope-from msch@snafu.de) Received: from dial-76-085.de.inter.net ([213.73.76.85] helo=current.best-eng.de) by havoc.eusc.inter.net with esmtp (Exim 3.36 #3) id 1CfnnC-0007SX-00; Sun, 19 Dec 2004 00:15:18 +0100 Received: from current.best-eng.de (localhost.best-eng.de [127.0.0.1]) by current.best-eng.de (8.13.1/8.13.1) with ESMTP id iBINFHm3001131; Sun, 19 Dec 2004 00:15:17 +0100 (CET) (envelope-from msch@snafu.de) Received: from localhost (localhost [[UNIX: localhost]]) by current.best-eng.de (8.13.1/8.13.1/Submit) id iBINFGbD001130; Sun, 19 Dec 2004 00:15:16 +0100 (CET) (envelope-from msch@snafu.de) X-Authentication-Warning: current.best-eng.de: matthias set sender to msch@snafu.de using -f From: Matthias Schuendehuette Organization: Micro$oft-free Zone To: freebsd-stable@freebsd.org Date: Sun, 19 Dec 2004 00:15:15 +0100 User-Agent: KMail/1.7.1 References: <41C48A6F.7000203@barnabas.dk> <1103409359.52279.2.camel@zappa.Chelsea-Ct.Org> In-Reply-To: <1103409359.52279.2.camel@zappa.Chelsea-Ct.Org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412190015.16449.msch@snafu.de> cc: Nikolaj Hansen Subject: Re: FreeBSD 5.3 and vinum upgrade #2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: msch@snafu.de List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Dec 2004 23:15:22 -0000 Am Samstag, 18. Dezember 2004 23:35 schrieb Paul Mather: > > The biggest problem you'll have is if your system suffers the ATA > "TIMEOUT - WRITE_DMA" woe that bedevils some of us under 5.3. When > that happens, your mirror will be knocked into a degraded state (half > of your mirrored plexes will be marked down) even though the drive is > okay. Unfortunately, without "setstate" being implemented in "gvinum" > to mark the drive as up, thereby allowing you to issue "gvinum > start"s for the "downed" plexes, there's little more you can do to > get the "failed" drive recognised as being in the "up" state other > than to reboot. [...] 'gvinum setstate' was MFCed from -current together with 'gvinum checkpatity' and 'gvinum rebuildparity' a week ago or so... So that should make it easier to handle these ATA-Problems... -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) PGP-Key at and ID: 0xDDFB0A5F