From owner-freebsd-fs@FreeBSD.ORG Wed Apr 18 18:02:03 2007 Return-Path: X-Original-To: fs@freebsd.org Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 77D0216A400 for ; Wed, 18 Apr 2007 18:02:03 +0000 (UTC) (envelope-from staalebk@ifi.uio.no) Received: from smtp.bluecom.no (smtp.bluecom.no [193.75.75.28]) by mx1.freebsd.org (Postfix) with ESMTP id 0C51C13C455 for ; Wed, 18 Apr 2007 18:02:02 +0000 (UTC) (envelope-from staalebk@ifi.uio.no) Received: from eschew.pusen.org (unknown [193.69.145.10]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.bluecom.no (Postfix) with ESMTP id AA30C16FB48; Wed, 18 Apr 2007 20:02:01 +0200 (CEST) Received: from chiller by eschew.pusen.org with local (Exim 4.50) id 1HeETg-0001iD-RI; Wed, 18 Apr 2007 20:02:00 +0200 Date: Wed, 18 Apr 2007 20:02:00 +0200 From: =?iso-8859-1?Q?St=E5le?= Kristoffersen To: "Rick C. Petty" Message-ID: <20070418180200.GA32061@eschew.pusen.org> References: <20070418104155.GA31727@eschew.pusen.org> <86hcrdlqak.fsf@dwp.des.no> <20070418144103.GB31727@eschew.pusen.org> <20070418155156.GB20441@keira.kiwi-computer.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20070418155156.GB20441@keira.kiwi-computer.com> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: fs@freebsd.org Subject: Re: ZFS + replacing failing hard-drive. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Apr 2007 18:02:03 -0000 On 2007-04-18 at 10:51, Rick C. Petty wrote: > On Wed, Apr 18, 2007 at 04:41:03PM +0200, St?le Kristoffersen wrote: > > > > > > I don't think you do. This appears to be a bug in the ata driver > > > which ZFS is particularly good at triggering. > > > > I first noticed the problems running UFS an the first partition, and I have > > tried the drive on all of the following controllers: > > atapci0: port 0xcf00-0xcf7f mem 0xfddff000-0xfddff07f,0xfddf8000-0xfddfbfff irq 19 at device 0.0 on pci4 > > atapci1: port 0xaf00-0xaf07,0xae00-0xae03,0xad00-0xad07,0xac00-0xac03,0xab00-0xab0f mem 0xfd9fe000-0xfd9fffff irq 17 at device 0.0 on pci6 > > atapci2: port 0xfa00-0xfa07,0xf900-0xf903,0xf800-0xf807,0xf700-0xf703,0xf600-0xf60f,0xf500-0xf50f irq 19 at device 31.2 on pci0 > > atapci3: port 0xf300-0xf307,0xf200-0xf203,0xf100-0xf107,0xf000-0xf003,0xef00-0xef0f,0xee00-0xee0f irq 19 at device 31.5 on pci0 > > > > Same problem on all. And to support my theory that the disk was bad the new > > disk does not behave badly, even after a zpool scrub. > > That doesn't prove the disk was/is "bad". Here I'm using the word "bad" to > mean the disk has had at least 1 non-recoverable failure (i.e. a bad area > on the platter surface was discovered and the drive was unable to remap > it). As new as SATA300 is, it is doubtful (although possible) that the > drive is "bad"/defective. The drive was new a couple of weeks ago, and it gave me errors almost from the beginning. > > Another issue is that even if all the drives support SATA300, and all the > > controllers does so as well, they still come up as SATA150 (except one). > > (And yeah, I have removed that jumper) > > ad8: 305245MB at ata4-master SATA300 > > ad10: 381554MB at ata5-master SATA150 > > ad14: 305245MB at ata7-master SATA150 > > ad15: 305245MB at ata7-slave SATA150 > > ad16: 305245MB at ata8-master SATA150 > > I've noticed this behavior on certain controllers (Intel in particular). > Which drives correspond to which controller cards? I've been swapping them around but right now: atapci0: port 0xcf00-0xcf7f mem 0xfddff000-0xfddff07f,0xfddf8000-0xfddfbfff irq 19 at device 0.0 on pci4 atapci1: port 0xaf00-0xaf07,0xae00-0xae03,0xad00-0xad07,0xac00-0xac03,0xab00-0xab0f mem 0xfd9fe000-0xfd9fffff irq 17 at device 0.0 on pci6 atapci1: AHCI Version 01.00 controller with 2 ports detected atapci2: port 0xfa00-0xfa07,0xf900-0xf903,0xf800-0xf807,0xf700-0xf703,0xf600-0xf60f,0xf500-0xf50f irq 19 at device 31.2 on pci0 atapci3: port 0xf300-0xf307,0xf200-0xf203,0xf100-0xf107,0xf000-0xf003,0xef00-0xef0f,0xee00-0xee0f irq 19 at device 31.5 on pci0 ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata1 at port 0x170-0x177,0x376 irq 15 on isa0 ata2: on atapci0 ata3: on atapci0 ata4: on atapci1 ata5: on atapci1 ata6: on atapci1 ata7: on atapci2 ata8: on atapci2 ata9: on atapci3 ata10: on atapci3 ad8: 305245MB at ata4-master SATA300 ad10: 381554MB at ata5-master SATA150 ad14: 305245MB at ata7-master SATA150 ad15: 305245MB at ata7-slave SATA150 ad16: 305245MB at ata8-master SATA150 -- Ståle Kristoffersen staalebk@ifi.uio.no