From owner-freebsd-geom@FreeBSD.ORG Mon Nov 29 11:57:22 2004 Return-Path: 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 2C24616A4CE for ; Mon, 29 Nov 2004 11:57:22 +0000 (GMT) Received: from zaphod.nitro.dk (port324.ds1-khk.adsl.cybercity.dk [212.242.113.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EEFA43D55 for ; Mon, 29 Nov 2004 11:57:19 +0000 (GMT) (envelope-from simon@zaphod.nitro.dk) Received: by zaphod.nitro.dk (Postfix, from userid 3000) id E616911A6B; Mon, 29 Nov 2004 12:57:17 +0100 (CET) Date: Mon, 29 Nov 2004 12:57:17 +0100 From: "Simon L. Nielsen" To: Terje Elde Message-ID: <20041129115717.GA753@zaphod.nitro.dk> References: <20041129114740.GD90910@calleigh.elde.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CE+1k2dSO48ffgeK" Content-Disposition: inline In-Reply-To: <20041129114740.GD90910@calleigh.elde.net> User-Agent: Mutt/1.5.6i cc: freebsd-geom@freebsd.org Subject: Re: mirror handling of broken harddrives X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 11:57:22 -0000 --CE+1k2dSO48ffgeK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004.11.29 12:47:40 +0100, Terje Elde wrote: > Given faulty hardware, resulting in: >=20 > ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=3D35170616 > ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=3D35170616 > ad0: FAILURE - READ_DMA timed out >=20 > How would this be handled by geom_mirror if it was a part of a two-plex > volume? I can show you from my log how it handles it :-) : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=3D152911 ad0: FAILURE - WRITE_DMA timed out GEOM_MIRROR: Request failed (error=3D5). ad0[WRITE(offset=3D78290432, lengt= h=3D16384)] GEOM_MIRROR: Device boot: provider ad0 disconnected. GEOM_MIRROR: Device boot: provider ad0 detected. GEOM_MIRROR: Device boot: rebuilding provider ad0. GEOM_MIRROR: Device boot: rebuilding provider ad0 finished. GEOM_MIRROR: Device boot: provider ad0 activated. So, it just works :-). Actually the mirror in question has rebuild itself like that many times, and I actually only noticed after quite a while :-). I actually had more or less the same (the ata errors) happen on another system, which uses ata(4) for RAID1, and there I had to manually rebuild the mirror... geom_mirror has just worked great for me, thanks Pawel! :-) --=20 Simon L. Nielsen --CE+1k2dSO48ffgeK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBqw6dh9pcDSc1mlERAorBAJ97A9ysQBAoaCTPOTMoG5dPWY9Y+wCfYmk7 SwdeBoAMnwGBvl7FAiP+LzI= =t4eM -----END PGP SIGNATURE----- --CE+1k2dSO48ffgeK--