From owner-freebsd-geom@FreeBSD.ORG Tue Feb 13 17:27:42 2007 Return-Path: X-Original-To: freebsd-geom@FreeBSD.org Delivered-To: freebsd-geom@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 79C7816A401 for ; Tue, 13 Feb 2007 17:27:42 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp8-g19.free.fr (smtp8-g19.free.fr [212.27.42.65]) by mx1.freebsd.org (Postfix) with ESMTP id 4784713C46B for ; Tue, 13 Feb 2007 17:27:42 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (tataz.chchile.org [82.233.239.98]) by smtp8-g19.free.fr (Postfix) with ESMTP id 99E344528; Tue, 13 Feb 2007 18:27:41 +0100 (CET) Received: from obiwan.tataz.chchile.org (unknown [192.168.1.25]) by tatooine.tataz.chchile.org (Postfix) with ESMTP id 968DC9D41F; Tue, 13 Feb 2007 17:28:43 +0000 (UTC) Received: by obiwan.tataz.chchile.org (Postfix, from userid 1000) id 861BC4063; Tue, 13 Feb 2007 18:28:43 +0100 (CET) Date: Tue, 13 Feb 2007 18:28:43 +0100 From: Jeremie Le Hen To: Oliver Fromme Message-ID: <20070213172843.GP64768@obiwan.tataz.chchile.org> References: <20070213110506.GL64768@obiwan.tataz.chchile.org> <200702131607.l1DG7uhU091519@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200702131607.l1DG7uhU091519@lurza.secnetix.de> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-geom@FreeBSD.org Subject: Re: gmirror or ata problem X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2007 17:27:42 -0000 Oliver, On Tue, Feb 13, 2007 at 05:07:56PM +0100, Oliver Fromme wrote: > Jeremie Le Hen wrote: > > FWIW, I had experienced this before likely because my drives went > > too warm (I am using gmirror as well). I've bought a couple of fan > > racks and the problem hasn't occured since then. > > Last week we got a real read error reported on the disk > (with a useful log entry, finally), so we arranged a > replacement disk. It has been working flawlessly so far. > > So maybe it was really the disk causing the trouble. > > However, the strange thing is that _no_ ATA errors were > logged at all previously. If gmirror disconnects a drive > because of ATA trouble (i.e. a read/write error), I would > expect that the ATA driver should report that read/write > error, shouldn't it? I can't remember if I had such messages. However I suspect the following messages to be issued by the ata layer: % Jan 29 19:20:26 pluto kernel: ad1: FAILURE - device detached % Jan 29 19:20:26 pluto kernel: subdisk1: detached % Jan 29 19:20:26 pluto kernel: ad1: detached BTW, this is is confirmed by grep(1): % jarjarbinks:tataz$ grep "device detached" /sys/dev/ata/* % /sys/dev/ata/ata-all.c: device_printf(request->dev, "FAILURE - device detached\n"); The following gmirror error messages is then an expected consequence. Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org >