From owner-freebsd-current@FreeBSD.ORG Thu Jul 26 00:51:59 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4E45116A418 for ; Thu, 26 Jul 2007 00:51:59 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from smtp02.dentaku.gol.com (smtp02.dentaku.gol.com [203.216.5.72]) by mx1.freebsd.org (Postfix) with ESMTP id 2378413C442 for ; Thu, 26 Jul 2007 00:51:59 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from pat.gol.co.jp ([203.216.1.191] helo=[127.0.0.1]) by smtp02.dentaku.gol.com with esmtpa (Dentaku) id 1IDra9-0002Uv-Tt for ; Thu, 26 Jul 2007 09:51:58 +0900 Message-ID: <46A7F02C.9000502@fusiongol.com> Date: Thu, 26 Jul 2007 09:51:56 +0900 From: Nathan Butcher User-Agent: Thunderbird 2.0.0.5 (Windows/20070716) MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.95.2 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV GOL X-Abuse-Complaints: abuse@gol.com Subject: Re: Promise SATA300 TX4 card issues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jul 2007 00:51:59 -0000 >I've got a ZFS pool setup, and when scrubbing the pool it comes up with > erratic CKSUM errors (for example, scrub once and get 7 errors, scrub > again immediately and get 53 more). I did a buildworld and buildkernel just yesterday with the latest CURRENT sources and I can confirm that I'm seeing the same problem. What is interesting is that didn't notice any hard system lockups. My system is amd64 with 2GB of RAM, four 500GB drives connected to my Promise SATA300 TX4 card in a raidz1 pool. For testing purposes, I have created a volume in my zpool, which houses a UFS file system created and accessed via GELI. I then use samba to copy data to and from the volume on another machine. While writing data to my volume, I am getting erratic CKSUM errors being "discovered" coming from my ZFS raidz1 (a look at zpool status after the write confirms this), and scrubbing the zpool just seems to discover more CKSUM errors. "zpool status" is telling me to replace some of my disks. This never happened before. I revert my kernel back to the old 200706 snapshot kernel and now the CKSUM errors are all gone. A fsck on my GELI UFS volume now produces no errors, and a scrub on my ZFS volume no longer produces CKSUM errors. The data I wrote to the volume is intact - so no data corruption as far as I can tell. It would be great if these issues could be solved for this card, as it is one of the cheapest 4-port SATA expansion cards out there for creating a zpool with. *SIGH* In the meantime I am going to have to stick with the 200706 snapshot kernel and userland, which is stable with this card.