Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id C650E650014 for ; Mon, 24 Nov 2008 12:14:05 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 51242-03 for ; Mon, 24 Nov 2008 12:14:03 -0400 (AST) X-Greylist: delayed 00:32:20.558004 by SQLgrey-1.7.6 Received: from h7.zynet2.co.uk (h7.zynet2.co.uk [212.24.80.7]) by mail.postgresql.org (Postfix) with ESMTP id AD7E064FFF8 for ; Mon, 24 Nov 2008 12:14:02 -0400 (AST) Received: from h93.zynet2.co.uk (h93.zynet2.co.uk [212.24.80.93]) by h7.zynet2.co.uk (Postfix) with ESMTP id B1F0C1BB856 for ; Mon, 24 Nov 2008 15:41:43 +0000 (GMT) Received: from h66.zynet2.co.uk (h66.zynet2.co.uk [212.24.80.66]) (Authenticated sender: simon) by h93.zynet2.co.uk (Postfix) with ESMTP id B0BC95E951C for ; Mon, 24 Nov 2008 15:41:43 +0000 (GMT) From: Simon Waters Organization: ZyNet Limited To: pgsql-performance@postgresql.org Subject: Re: Perc 3 DC Date: Mon, 24 Nov 2008 15:41:43 +0000 User-Agent: KMail/1.9.9 References: <911105.66836.qm@web23605.mail.ird.yahoo.com> In-Reply-To: <911105.66836.qm@web23605.mail.ird.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200811241541.43542.simonw@zynet.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200811/233 X-Sequence-Number: 31964 On Monday 24 November 2008 14:49:17 Glyn Astill wrote: > --- On Mon, 24/11/08, Steve Clark wrote: > > > Yeah the battery's on it, that and the 128Mb is > > > > really the only reason I thought I'd give it a whirl. > > > > > > Is the battery functioning? We found that the unit had to > > be on and charged before write back caching > > would work. > > Yeah the battery is on there, and in the BIOS it says it's "PRESENT" and > the status is "GOOD". Sorry I deleted the beginning of this on getting back from a week off. Writeback is configurable. You can enabled write back caching when the unit is not charged if you like. It is offered when you create the array (and can be changed later). It is arguably a silly thing to do, but it is an option. I have some reasonable performance stats for this card assuming you have a suitably recent version of the driver software, DELL use to ship with a Linux kernel that had a broken driver for this card resulting is very poor performance (i.e. substantially slower than software RAID). I have a note never to use with Linux before 2.6.22 as the LSI driver bundled had issues, DELL themselves shipped (if you asked "why is performance so bad") a Redhat kernel with a later driver for the card than the official Linux kernel. That said a couple of weeks back ours corrupted a volume on replacing a dead hard disk, so I'm never touching these cheap and tacky LSI RAID cards ever again. It is suppose to just start rebuilding the array when you insert the replacement drive, if it doesn't "just work" schedule some down time and figure out exactly why, don't (for example) blindly follow the instructions in the manual on what to do if it doesn't "just work".