Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 379DA2E0039 for ; Mon, 3 Mar 2008 00:23:29 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 74974-03 for ; Mon, 3 Mar 2008 00:23:26 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from gv-out-0910.google.com (gv-out-0910.google.com [216.239.58.184]) by postgresql.org (Postfix) with ESMTP id 57E7B2E002C for ; Mon, 3 Mar 2008 00:23:26 -0400 (AST) Received: by gv-out-0910.google.com with SMTP id y18so3025514gvf.7 for ; Sun, 02 Mar 2008 20:23:25 -0800 (PST) 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=JRtgm7uObmNUUnlF3iX/pAqGvkEd8VoeAc5beo9q4MM=; b=nhg3H4fwsBbvxRQBDx70JkjUD6+mhLARTK9sqlTv4jiiYEybUDKrIKkysN1gvKStvLmUL6LDuhacW2C9AlU0pE5UDY/Ai02cxwDPotHt6Vh9CKTAn2pDDpkFQDO+0OhN5CzfLNL9YkIfYukq/iUlhSRDdFVhaBOl0UIA3FQJt2I= 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=tIpwHvmly4K56gCjXHXJVVk80fa5GRjChvPHR3mN3vcBrKKp7C3EPoCV01Zih4FZfcQ7ovlzvjj3+NYMpOBpsiDlMbVDSE81k7zBkhd+T2yeq7q6lDcwMcWVTsWq5MDXnDlp2a8Xs9J8xv+UTcf9fkXLXjfRhP5TQV9gAqbJjRU= Received: by 10.114.170.1 with SMTP id s1mr2079824wae.54.1204518203380; Sun, 02 Mar 2008 20:23:23 -0800 (PST) Received: by 10.114.133.6 with HTTP; Sun, 2 Mar 2008 20:23:23 -0800 (PST) Message-ID: Date: Sun, 2 Mar 2008 22:23:23 -0600 From: "Scott Marlowe" To: "Vivek Khera" Subject: Re: How to choose a disc array for Postgresql? Cc: pgsql-performance@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <721b21dc0803012337u55ddaa13l5517816659f8e100@mail.gmail.com> 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: 200803/19 X-Sequence-Number: 28973 On Sun, Mar 2, 2008 at 9:11 PM, Vivek Khera wrote: > > On Mar 2, 2008, at 2:37 AM, Steve Poe wrote: > > > I need to consider a vendor for the new disc array (6- > > to 8 discs). The local vendor (in the San Francisco Bay Area), > > I've not been completely pleased with, so I am considering using > > Dell storage connecting to an retail version LSI MegaRAID 320-2X card. > > > > Anyone use any vendors that have been supportive of Postgresql? > > I've been 1000% satisfied with Partners Data for my RAID systems. I > connect to the host boxes with a fibre channel. They've gone above > and beyond expectations for supporting my FreeBSD systems. I don't > know if/how they support postgres as I never asked for that help. > Their prices are excellent, too. > > As for your plan to hook up Dell storage to a 320-2x card, the last > time I did that, the lsi card complained that one of the drives in the > 14-disk chassis was down. Identical on two different arrays I had. > Dell swapped nearly every single part, yet the LSI card still > complained. I had to drop the drives to U160 speed to get it to even > recognize all the drives. Is there still some advantage to U320 over SAS? I'm just wondering why one would be building a new machine with U320 instead of SAS nowadays. And I've never had any of the problems you list with LSI cards. The only issue I've seen is mediocre RAID-10 performance on their cards many years ago, when I was testing them for our database server. Adaptec controllers, especially RAID controllers have been nothing but problematic for me, with random lockups every month or two. Just enough to make it really dangerous, not often enough to make it easy to troubleshoot. In those systems the lockup problems were solved 100% by switching to LSI based controllers.