From owner-freebsd-current@FreeBSD.ORG Fri Jun 9 19:33:20 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 826B716A41A for ; Fri, 9 Jun 2006 19:33:20 +0000 (UTC) (envelope-from cbh-freebsd-current@groups.chrishedley.com) Received: from lon-mail-3.gradwell.net (lon-mail-3.gradwell.net [193.111.201.127]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6427D43D98 for ; Fri, 9 Jun 2006 19:33:11 +0000 (GMT) (envelope-from cbh-freebsd-current@groups.chrishedley.com) Received: from 53-233.adsl.zetnet.co.uk ([194.247.53.233] helo=mail.chrishedley.com country=GB ident=postmaster*pop3^chrishedley&com) by lon-mail-3.gradwell.net with esmtpa (Gradwell gwh-smtpd 1.219) id 4489ccf5.67c0.1df for current@freebsd.org; Fri, 9 Jun 2006 20:33:09 +0100 (envelope-sender ) Received: from localhost (localhost [127.0.0.1]) by mail.chrishedley.com (Postfix) with ESMTP id C5AC2CCAF; Fri, 9 Jun 2006 20:33:07 +0100 (BST) X-Virus-Scanned: amavisd-new at chrishedley.com Received: from mail.chrishedley.com ([127.0.0.1]) by localhost (mail.chrishedley.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 06JTeXRj72dK; Fri, 9 Jun 2006 20:33:05 +0100 (BST) Received: from aga.cbhnet (aga.cbhnet [192.168.1.16]) by mail.chrishedley.com (Postfix) with ESMTP id C962ECCAE; Fri, 9 Jun 2006 20:33:05 +0100 (BST) Date: Fri, 9 Jun 2006 20:33:07 +0100 (BST) From: Chris Hedley X-X-Sender: cbh@aga.cbhnet To: Doug White In-Reply-To: <20060609120159.I60598@carver.gumbysoft.com> Message-ID: <20060609202536.Y829@aga.cbhnet> References: <20060609163735.D829@aga.cbhnet> <20060609120159.I60598@carver.gumbysoft.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@freebsd.org Subject: Re: aac0: COMMAND 0xffffffffxxxxxxxx TIMEOUT AFTER xx SECONDS 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: Fri, 09 Jun 2006 19:33:20 -0000 On Fri, 9 Jun 2006, Doug White wrote: > On Fri, 9 Jun 2006, Chris Hedley wrote: >> I've been receiving this message quite a lot lately if I put my Adaptec >> 2410SA aac controller under really heavy load. A quick look at the >> archives suggests that it used to be a problem a couple of years ago, but >> was apparently fixed. Personally I've had no bother with it until a few >> months ago when I upgraded my version of -CURRENT, at which point it >> started misbehaving. > > I assume you've checked cabling and termination? Frequently, driver updates > can improve performance which means less tolerance for marginal > configurations. The 2410SA uses SATA discs (I was trying to get SCSI performance on the cheap, ever the optimist!) so I'm assuming that the cables are okay. At least there's no user-breakable termination settings for me to worry about... >> I'm also wondering if I might not be better off actually replacing the card >> with something better, or at least something better suited to FreeBSD: with >> the discs' and controller's write-caching turned off, the 2410SA is >> s-l-o-w, about 6MB/s for contiguous writes to an array (either RAID-5 or >> RAID-10) (benchmarked using the admittedly somewhat crude "dd various block >> sizes to/from a /dev entry" technique), although reads are acceptable at >> ~50-60MB/s, if not especially earth-shattering. Any suggestions (for >> something inexpensive! If money were no object I'd've gone for a SCSI-only >> system), or might I just as well stick with the 2410SA? > > 6MB/s sounds like you aren't getting any help from the card's write cache; > its having to do stripe reads to recalculate parity instead of doing full > stripe writes. Many cards disable write-back cache if the battery module > isn't present -- make sure you have one and its working. /dev accesses also > use physio so you don't get any benefit from write combining in the > filesystem layer. I've deliberately turned off write-caching because the 2410SA doesn't support battery-backed memory. I'm not sure if it's really necessary to disable it, but having experienced the odd disc crash in the past I've become a little paranoid about my data... > Also, in general, hardware RAID beats PCI RAID, hands down. In my case, software raid beats it too! I have my "fast discs" attached to an old 3960 controller and mirror them with gmirror, and the write performance is an order of magnitude better than the 2410SA, which tells me that something somewhere must be wrong. I know I shouldn't really expect SCSI performance from SATA discs, but this seems a bit much to me (I also have write-caching turned off on my SCSI discs, but I have enabled tagged queueing). I'm still slightly uncomfortable with the idea of software RAID, but it hasn't lost anything yet, in spite of a few "unplanned outages". Chris.