From owner-freebsd-geom@FreeBSD.ORG Mon Dec 21 11:46:27 2009 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D97ED1065670 for ; Mon, 21 Dec 2009 11:46:27 +0000 (UTC) (envelope-from gcubfg-freebsd-geom@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 96BE58FC13 for ; Mon, 21 Dec 2009 11:46:27 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1NMgiT-0001u6-ND for freebsd-geom@freebsd.org; Mon, 21 Dec 2009 12:46:21 +0100 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 21 Dec 2009 12:46:21 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 21 Dec 2009 12:46:21 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-geom@freebsd.org From: Ivan Voras Date: Mon, 21 Dec 2009 12:46:01 +0100 Lines: 20 Message-ID: References: <20091220151453.3dbe738e@johnea.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.23 (X11/20091210) In-Reply-To: <20091220151453.3dbe738e@johnea.net> Sender: news Subject: Re: errrors resyncronizing mirror with new disk 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: Mon, 21 Dec 2009 11:46:27 -0000 johnea wrote: > Hello, > > Recently a drive started to have READ_DMA failures and drop out of the gmirror. > > While synching the replacement drive to the mirror, a WRITE error occured and terminated the sync. > > A second attempt to sync completed but left the drive generating READ errors. > > The third time the drive was inserted in the mirror the operation completed and no further errors have occured. > > R'ingTFM and extensive scroogling have not yielded an explanation. > > Is this expected behaviour? Should I suspect this drive? > (it's brand new, but the "old" one was only 9 months) Yes. Probably either the drives or the power unit. > Additionally smartctl on the new drive continues to indicate no errors. > (it did indicate each of the read errors on the old drive)