Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 65C8B1337CA7 for ; Wed, 16 Feb 2011 17:14:54 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 85548-01 for ; Wed, 16 Feb 2011 21:14:47 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from spinlock.commandprompt.com (host-215.commandprompt.net [207.173.203.215]) by mail.postgresql.org (Postfix) with ESMTP id C62B21337C39 for ; Wed, 16 Feb 2011 17:13:15 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by spinlock.commandprompt.com (Postfix) with ESMTP id 349CA348025; Wed, 16 Feb 2011 13:13:15 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at commandprompt.com Received: from spinlock.commandprompt.com ([127.0.0.1]) by localhost (spinlock.commandprompt.com.commandprompt.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oq1CFMrfxGs5; Wed, 16 Feb 2011 13:13:12 -0800 (PST) Received: from [192.168.1.101] (71-94-248-62.dhcp.mdfd.or.charter.com [71.94.248.62]) by spinlock.commandprompt.com (Postfix) with ESMTPSA id AE983348022; Wed, 16 Feb 2011 13:13:12 -0800 (PST) Subject: Re: Postgres on NAS/NFS From: "Joshua D. Drake" Reply-To: jd@commandprompt.com To: Greg Smith Cc: Bryan Keller , pgsql-admin@postgresql.org In-Reply-To: <4D5C39ED.9040609@2ndquadrant.com> References: <9424C7B4-672D-4C64-BE6A-699708981C0B@gmail.com> <4D5C39ED.9040609@2ndquadrant.com> Content-Type: text/plain; charset="UTF-8" Organization: Command Prompt, Inc. Date: Wed, 16 Feb 2011 13:12:39 -0800 Message-ID: <1297890759.991.154.camel@jd-desktop> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201102/155 X-Sequence-Number: 36794 On Wed, 2011-02-16 at 15:56 -0500, Greg Smith wrote: > Bryan Keller wrote: > > It sounds like NFS is a viable solution nowadays. I a still going to shoot for using iSCSI, given it is a block-level protocol rather than file-level, it seems to me it would be better suited to database I/O. > > > > Please digest carefully where Joe Conway pointed out that it took them > major kernel-level work to get NFS working reliably on Linux. On > anything but Solaris, I consider NFS a major risk still; nothing has > improved "nowadays" relative to when people used to report regular > database corruption running it on other operating systems. Make sure > you read > http://www.time-travellers.org/shane/papers/NFS_considered_harmful.html > and mull over the warnings in there before you assume it will work, too. > > I don't think I've ever heard from someone happy with an iSCSI > deployment, either. The only way you could make an NFS+iSCSI storage > solution worse is to also use RAID5 on the NAS. > > I'd suggest taking a look at > http://wiki.postgresql.org/wiki/Shared_Storage and consider how you're > going to handle fencing issues as well here. One of the reasons SANs > tend to be preferred in this area is because fencing at the > fiber-channel switch level is pretty straightforward. DAS running over > fiber-channel can offer the same basic features though, it's just not as > common to use a switch in that environment. In short, use DAS or a SAN. iSCSI suffers from all kinds of performance issues and NFS is just Michael Myers scary. With DAS systems able to handle up 192 drives over 6Gb/s a second these days, combined with a volume manager you can solve a lot of problems without breaking the bank. JD -- PostgreSQL.org Major Contributor Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579 Consulting, Training, Support, Custom Development, Engineering http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt