ZFS + replacing failing hard-drive.

[Ståle Kristoffersen]

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: <SiI 3132 SATA300 controller> port 0xcf00-0xcf7f mem 0xfddff000-0xfddff07f,0xfddf8000-0xfddfbfff irq 19 at device 0.0 on pci4
> > atapci1: <JMicron JMB363 SATA300 controller> port 0xaf00-0xaf07,0xae00-0xae03,0xad00-0xad07,0xac00-0xac03,0xab00-0xab0f mem 0xfd9fe000-0xfd9fffff irq 17 at device 0.0 on pci6
> > atapci2: <Intel ICH8 SATA300 controller> port 0xfa00-0xfa07,0xf900-0xf903,0xf800-0xf807,0xf700-0xf703,0xf600-0xf60f,0xf500-0xf50f irq 19 at device 31.2 on pci0
> > atapci3: <Intel ICH8 SATA300 controller> 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 <Seagate ST3320620AS 3.AAC> at ata4-master SATA300
> > ad10: 381554MB <Seagate ST3400620AS 3.AAK> at ata5-master SATA150
> > ad14: 305245MB <Seagate ST3320620AS 3.AAC> at ata7-master SATA150
> > ad15: 305245MB <Seagate ST3320620AS 3.AAC> at ata7-slave SATA150
> > ad16: 305245MB <Seagate ST3320620AS 3.AAE> 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: <SiI 3132 SATA300 controller> port 0xcf00-0xcf7f mem 0xfddff000-0xfddff07f,0xfddf8000-0xfddfbfff irq 19 at device 0.0 on pci4
atapci1: <JMicron JMB363 SATA300 controller> 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: <Intel ICH8 SATA300 controller> port 0xfa00-0xfa07,0xf900-0xf903,0xf800-0xf807,0xf700-0xf703,0xf600-0xf60f,0xf500-0xf50f irq 19 at device 31.2 on pci0
atapci3: <Intel ICH8 SATA300 controller> 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: <ATA channel 0> on atapci0
ata3: <ATA channel 1> on atapci0
ata4: <ATA channel 0> on atapci1
ata5: <ATA channel 1> on atapci1
ata6: <ATA channel 2> on atapci1
ata7: <ATA channel 0> on atapci2
ata8: <ATA channel 1> on atapci2
ata9: <ATA channel 0> on atapci3
ata10: <ATA channel 1> on atapci3
ad8: 305245MB <Seagate ST3320620AS 3.AAC> at ata4-master SATA300
ad10: 381554MB <Seagate ST3400620AS 3.AAK> at ata5-master SATA150
ad14: 305245MB <Seagate ST3320620AS 3.AAC> at ata7-master SATA150
ad15: 305245MB <Seagate ST3320620AS 3.AAC> at ata7-slave SATA150
ad16: 305245MB <Seagate ST3320620AS 3.AAE> at ata8-master SATA150

-- 
Ståle Kristoffersen
staalebk at ifi.uio.no