X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 742AED1B1CB for ; Tue, 22 Jun 2004 10:21:21 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 27180-07 for ; Tue, 22 Jun 2004 13:21:22 +0000 (GMT) Received: from bayswater1.ymogen.net (host-154-240-27-217.pobox.net.uk [217.27.240.154]) by svr1.postgresql.org (Postfix) with ESMTP id 3E3F2D1B169 for ; Tue, 22 Jun 2004 10:21:16 -0300 (ADT) Received: from solent (82-68-95-1.dsl.in-addr.zen.co.uk [82.68.95.1]) by bayswater1.ymogen.net (Postfix) with ESMTP id 25CD49E123; Tue, 22 Jun 2004 14:21:18 +0100 (BST) From: "Matt Clark" To: "'Christopher Browne'" , Subject: Re: Postgres over Linux NBD or NFS Date: Tue, 22 Jun 2004 14:21:10 +0100 Message-ID: <000001c4585b$caac3c50$8300a8c0@solent> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/222 X-Sequence-Number: 7280 How about iSCSI? This is exactly what it's for - presenting a bunch of remote SCSI hardware as if it were local.=20=20 There are several reference implementations on SourceForge from Intel, Cisco & others. I've never tried it myself, but I would if I had the need. And let's face it there are some very big players selling very pricey kit that uses it, so you should have pretty high confidence that the fundamentals are strong. M > The other goal is to be able to stick LOTS of disk into one=20 > box, and dole it out to multiple servers. It's more=20 > expensive to set up and manage 3 RAID arrays than it is to=20 > set up and manage just 1, because you have to manage 3 sets=20 > of disk hardware rather than 1. [snip] > The "poor man's approach" involves trying to fake this by=20 > building a "disk box" running Linux that exports the storage=20 > either as a filesystem (using NFS) or as disk blocks (NBD).=20=20 > NFS clearly doesn't provide the filesystem semantics needed=20 > to get decent reliability; with NBD, it's not clear what happens :-(.