From owner-freebsd-geom@FreeBSD.ORG Wed Aug 2 18:30:03 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E83516A4E0 for ; Wed, 2 Aug 2006 18:30:03 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (megan.kiwi-computer.com [63.224.10.3]) by mx1.FreeBSD.org (Postfix) with SMTP id CA28A43D45 for ; Wed, 2 Aug 2006 18:30:02 +0000 (GMT) (envelope-from rick@kiwi-computer.com) Received: (qmail 14335 invoked by uid 2001); 2 Aug 2006 18:30:01 -0000 Date: Wed, 2 Aug 2006 13:30:01 -0500 From: "Rick C. Petty" To: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <20060802183001.GA14279@megan.kiwi-computer.com> References: <44D06650.1030803@quip.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44D06650.1030803@quip.cz> User-Agent: Mutt/1.4.2.1i Cc: freebsd-geom@freebsd.org Subject: Re: gmirror Cannot add disk ad5 to gm0 (error=22) X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd@kiwi-computer.com List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Aug 2006 18:30:03 -0000 On Wed, Aug 02, 2006 at 10:46:08AM +0200, Miroslav Lachman wrote: > > Aug 1 00:03:42 track kernel: ad5: TIMEOUT - WRITE_DMA48 retrying (1 > retry left) LBA=290279525 Out of curiosity-- what's the dmesg output of your ATA controllers? > I tried smartctl -a /dev/ad4 and smartctl -a /dev/ad5, but does not see > any errors. Did you have SMART enabled in the BIOS? > If I use gmirror activate -v gm0 ad5 I got > Aug 2 10:24:03 track kernel: GEOM_MIRROR: Component ad5 (device gm0) > broken, skipping. > Aug 2 10:24:03 track kernel: GEOM_MIRROR: Cannot add disk ad5 to gm0 > (error=22). It's already activated, so you can't add it again (as the message states). > I can successfuly mount partitions from drive ad5 like this > mount /dev/ad5s2d /mnt > > (Aug 2 10:35:21 track kernel: WARNING: /vol0 was not properly dismounted) > > And read any files from this drive. That shouldn't be a surprise-- the disks themselves didn't fail, only writing to them (possibly under heavy load?) failed-- and gmirror dropped the disks. The first disk drop was ok-- the mirror should still work in DEGRADED state. The second drop was critical which is why your system broke. Mounting the disks individually will work of course. > Can anybody tell me, where is the problem / how can I found what is wrong? What's the output of "gmirror status" ?? I suspect on a reboot, gmirror will try to synchronize ad4 to ad5 (since ad5 was the first to drop). Once that is complete, gmirror won't be DEGRADED anymore. -- Rick C. Petty