Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 3CBEF650556 for ; Tue, 15 Jul 2008 12:45:25 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 71243-07 for ; Tue, 15 Jul 2008 12:44:29 -0300 (ADT) Received: from mx1.hub.org (mx1.hub.org [200.46.208.106]) by postgresql.org (Postfix) with ESMTP id E877365065D for ; Tue, 15 Jul 2008 12:44:35 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.174]) by mx1.hub.org (Postfix) with ESMTP id DC3F2B07ADF for ; Tue, 15 Jul 2008 12:44:28 -0300 (ADT) Received: by wf-out-1314.google.com with SMTP id 25so4630103wfc.28 for ; Tue, 15 Jul 2008 08:43:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=UUiO1EAK/shn6wRBnseplArlv7WI5qxZJgfK3xzkRD8=; b=fyMDwIN0m/8Lp7GfX9znlfeN57VcgJ0t7VwZvWi4ciGvwn8WjijTMjmL9r/4HlDvOa K9/9h9i2OwyYNm0iamqpS2/tF6HObTDHsiLxx+ihXQqOCvZPhd62lSpOJw8q/lXiLxak pgsRWe3Wv3AcUR8LhTAC9TWu5tgoEZicEAk44= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=pgWaxS3lrE3nB77J/ZOcorx8gaSMr0cNV2DeSnL4fkmD8+ORjKIWpwUBcC8Jz0xD8q fwIv07K0ZuymgcWDWEYIX0eRS0vyx0NZfFMmO8gfYudeL1D7qu1P5vwgR3S1SRqzg0cu QYdeDVeWugIl8IzZmC37c1aQOTwWrO/lPpJLk= Received: by 10.143.14.16 with SMTP id r16mr4692936wfi.122.1216133179467; Tue, 15 Jul 2008 07:46:19 -0700 (PDT) Received: by 10.142.242.21 with HTTP; Tue, 15 Jul 2008 07:46:19 -0700 (PDT) Message-ID: Date: Tue, 15 Jul 2008 07:46:19 -0700 From: "Jeffrey Baker" To: "Greg Smith" Subject: Re: 3ware vs Areca Cc: "Pgsql performance" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <581D2333-E731-4843-BC31-39840E272C62@torgo.978.org> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200807/133 X-Sequence-Number: 30733 On Mon, Jul 14, 2008 at 9:13 PM, Greg Smith wrote: > On Fri, 11 Jul 2008, Jeffrey Baker wrote: > >> Their firmware is, frankly, garbage. In more than one instance we >> have had the card panic when a disk fails, which is obviously counter >> to the entire purpose of a RAID. We finally removed the Areca >> controllers from our database server and replaced them with HP P800s. > > Can you give a bit more detail here? If what you mean is that the driver > for the card generated an OS panic when a drive failed, that's not > necessarily the firmware at all. I know I had problems with the Areca cards > under Linux until their driver went into the mainline kernel in 2.6.19, all > kinds of panics under normal conditions. Haven't seen anything like that > with later Linux kernels or under Solaris 10, but then again I haven't had a > disk failure yet either. Well, it is difficult to tell if the fault is with the hardware or the software. No traditional kernel panic has been observed. But most recently in my memory we had an Areca HBA which, when one of its WD RE-2 disks failed, completely stopped responding to both the command line and the web management interface. Then, i/o to that RAID became increasingly slower, and slower, until it stopped serving i/o at all. At that point it was not relevant that the machine was technically still running. We have another Areca HBA that starts throwing errors up the SCSI stack if it runs for more than 2 months at a time. We have to reboot it on a schedule to keep it running. -jwb