From owner-freebsd-stable@FreeBSD.ORG Mon Feb 19 08:50:03 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2049816A401 for ; Mon, 19 Feb 2007 08:50:03 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id A157713C478 for ; Mon, 19 Feb 2007 08:50:02 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.13.8/8.13.8) with ESMTP id l1J8o14C040599; Mon, 19 Feb 2007 11:50:01 +0300 (MSK) (envelope-from marck@rinet.ru) Date: Mon, 19 Feb 2007 11:50:01 +0300 (MSK) From: Dmitry Morozovsky To: freebsd-stable@freebsd.org, marck@rinet.ru In-Reply-To: <200702190814.l1J8E5Qp013045@lurza.secnetix.de> Message-ID: <20070219114333.L31764@woozle.rinet.ru> References: <200702190814.l1J8E5Qp013045@lurza.secnetix.de> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (woozle.rinet.ru [0.0.0.0]); Mon, 19 Feb 2007 11:50:01 +0300 (MSK) Cc: Subject: Re: gmirror: degraded @ 100% X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Feb 2007 08:50:03 -0000 On Mon, 19 Feb 2007, Oliver Fromme wrote: OF> Dmitry Morozovsky wrote: OF> > root@office:/usr/local/etc# gmirror status m0g OF> > Name Status Components OF> > mirror/m0g DEGRADED ad4g OF> > ad6g (100%) OF> OF> It seems that the second disk is broken and locks up the OF> channel near the end of the disk. OF> OF> You could try to remove the drive from the mirror and OF> run dd(1) on it. If the dd command also hangs near the OF> end of the disk, then you should definitely get a new OF> disk drive. OF> OF> If the dd command finishes without errors (and displays OF> the correct number of transfered blocks), then I guess OF> there must be a bug in gmirror. This was my first guess, and I did exactly the same steps. Actually, there was kernel panic just a couple minutes after my first mail, but kernel has refused to either dump or even reboot. Offending process was, as expected, g_mirror m0g, but I was unable to write down parameters (serial console was defunct at the moment). What is wondering me, after reboot m0g finishes syncing successfully. I did recoverdisk /dev/ad6 /dev/null, and it finished without any error. Now recoverdisk /dev/ad4 /dev/null if working. What is also making me nervous: smartctl on both bisks reports bad SMART checksum, and refuses to start any tests, reporting test already in progress, 40% remaining. I suppose I'll change both drives ASAP. However, I'm still conserning geom_mirror bug(s) in corner cases, where some [not-so]-error conditions exist. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------