Date: Fri, 20 Apr 2007 09:14:06 +1000 From: Antony Mawer <fbsd-fs@mawer.org> To: David Cecil <david.cecil@nokia.com> Cc: Dag-Erling Sm?rgrav <des@des.no>, rick-freebsd@kiwi-computer.com, piso@freebsd.org, fs@freebsd.org Subject: Re: ZFS + replacing failing hard-drive. Message-ID: <4627F7BE.5090606@mawer.org> In-Reply-To: <4627EC02.8070103@nokia.com> References: <20070418104155.GA31727@eschew.pusen.org> <86hcrdlqak.fsf@dwp.des.no> <20070418144103.GB31727@eschew.pusen.org> <20070418155156.GB20441@keira.kiwi-computer.com> <20070418180200.GA32061@eschew.pusen.org> <86odlku5xg.fsf@dwp.des.no> <20070419173316.GA57227@keira.kiwi-computer.com> <4627EC02.8070103@nokia.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 20/04/2007 8:24 AM, David Cecil wrote: > ext Rick C. Petty wrote: >> On Thu, Apr 19, 2007 at 10:25:31AM +0200, Dag-Erling Sm?rgrav wrote: >> >>> Yes. I have four brand new disks which are giving me DMA timeouts all >>> the time. >>> >>> There seem to be bugs in (or in relation with) the ata driver which >>> have surfaced only recently. >>> >>> Now that I think about it - could this be related to interrupt >>> filtering? Piso? If the ata driver is losing interrupts, it's no >>> wonder the transfers are timing out. >>> >> >> What do you mean by recently? I've seen this problem which started >> around >> 5.4-RELEASE (perhaps earlier) and on, including 6.0-R thru 6.2-stable >> as of >> a few weeks ago. Would the interrupt filtering be present on these >> systems? > > I would like to second Rick's comments. I've certainly seen the problem > in 6.0 and 6.1, and replacing older disks with new ones hasn't rectified > the problem. > > Regards, > Dave Just another "me too". I've seen (S)ATA-related problems on 6.x (mostly 6.0) based machines, in some cases these appear to have been physical drive errors, but I haven't been able to verify each individual case. I don't know if quality control is sorely lacking on newer SATA drives or if it's something else... it has caused me to question whether or not there might be a driver/OS level issue... --Antony
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4627F7BE.5090606>