Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 03 Jul 2007 10:35:24 +0900
From:      Nathan Butcher <n-butcher@fusiongol.com>
To:        =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= <des@des.no>
Cc:        freebsd-current@freebsd.org
Subject:   Re: Promise SATA300 TX4 card issues
Message-ID:  <4689A7DC.1070604@fusiongol.com>
In-Reply-To: <86wsxibxc2.fsf@dwp.des.no>
References:  <4679CE35.8080907@fusiongol.com> <86wsxibxc2.fsf@dwp.des.no>

next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Smørgrav wrote:
> Nathan Butcher <n-butcher@fusiongol.com> writes:
>> I've been having problems with my ZFS pool consisting of 4 drives hooked
>> up to my Prmoise SATA 300TX4 controller. It had been working fine until
>> to around the 19th of this month, and then I started seeing error
>> messages whenever I tried to write lots of data to ZFS..... followed by
>> a nasty lockup with no other debugging information of which to speak of.
> 
> This is a recurring problem with ZFS and ata disks.  It appears that the
> ata driver doesn't like the ATA_FLUSHCACHE command very much, and ZFS
> uses it a lot.  Turning off atime helps, as does turning off ata write
> caching (hw.ata.wc=0 in loader.conf) - I still get timeouts and
> transient hangs once in a while, but my server no longer crashes:

Thanks for your input. I had my suspicions about the ata driver.

Perhaps I should clarify my situation however. I rebuilt my kernel and
world on the 15th, and my server was working fine until the 19th when I
rebuilt my kernel and world again and then started seeing issues.
It seems to me that some changes must have been made in the ata driver
(assuming that's what it is) between updates which caused this borkage
to happen. When I rolled back to the 200706 snapshot sources, once again
my server is stable.

Mind that my server has a core2 duo running amd64 with 2GB of memory.

I noticed some updates to the ata driver code during the past month, so
I will try updating to the next snapshot sources (200707) when it is
released to see if this issue has been fixed.... otherwise I'm rolling
back to 200706 sources.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4689A7DC.1070604>