From owner-freebsd-geom@FreeBSD.ORG Wed Jan 31 20:12:04 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 1F37E16A400 for ; Wed, 31 Jan 2007 20:12:04 +0000 (UTC) (envelope-from simon@zaphod.nitro.dk) Received: from mx.nitro.dk (zarniwoop.nitro.dk [83.92.207.38]) by mx1.freebsd.org (Postfix) with ESMTP id CC11513C46B for ; Wed, 31 Jan 2007 20:12:03 +0000 (UTC) (envelope-from simon@zaphod.nitro.dk) Received: from zaphod.nitro.dk (unknown [192.168.3.39]) by mx.nitro.dk (Postfix) with ESMTP id 046402D4951; Wed, 31 Jan 2007 20:11:30 +0000 (UTC) Received: by zaphod.nitro.dk (Postfix, from userid 3000) id 2D5AA11434; Wed, 31 Jan 2007 21:12:02 +0100 (CET) Date: Wed, 31 Jan 2007 21:12:02 +0100 From: "Simon L. Nielsen" To: Oliver Fromme Message-ID: <20070131201201.GB973@zaphod.nitro.dk> References: <200701300851.l0U8pEkO005250@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200701300851.l0U8pEkO005250@lurza.secnetix.de> User-Agent: Mutt/1.5.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: Wed, 31 Jan 2007 20:12:04 -0000 On 2007.01.30 09:51:14 +0100, Oliver Fromme wrote: > This is strange. gmirror just detached one of its disks > for no apparent reason. I've built a mirror consisting of > the components ad0 and ad1 (both SATA drives). It has > been running fine. This is RELENG_6 from 2006-12-20. > > Yesterday evening ad1 was detached. There is no other > error message logged on console or in the logs (i.e. no > I/O error such as a bad sector or anything). There was > no particularly high load at that time. In fact, the > machine had been under much higher load before, without > anything bad happening. > > This is from the logs: > > Jan 29 19:10:13 pluto -- MARK -- > 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 > Jan 29 19:20:26 pluto kernel: GEOM_MIRROR: Cannot write metadata on ad1 (device=gm0, error=6). > Jan 29 19:20:26 pluto kernel: GEOM_MIRROR: Cannot update metadata on disk ad1 (error=6). > Jan 29 19:20:26 pluto kernel: GEOM_MIRROR: Cannot update metadata on disk ad1 (error=6). > Jan 29 19:20:26 pluto kernel: GEOM_MIRROR: Device gm0: provider ad1 disconnected. > Jan 29 19:50:13 pluto -- MARK -- I have seen similar problems on my graid3. I think it's simply the disk which stops responding to commands, or at least ata(4) can't talk to the disk anymore... I see it on: ad10: 305245MB at ata5-master SATA150 ad12: 305245MB at ata6-master SATA150 ad14: 305245MB at ata7-master SATA150 After a reboot everything seems fine again and my RAID is rebuilt. I don't know why it happens, but it sucks :-/. I'm running 7-CURRENT BTW. -- Simon L. Nielsen