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 272035E46EE for ; Thu, 26 Aug 2004 16:54:15 -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 95189-02 for ; Thu, 26 Aug 2004 19:54:12 +0000 (GMT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by svr1.postgresql.org (Postfix) with ESMTP id 2F18A5E46D1 for ; Thu, 26 Aug 2004 16:54:08 -0300 (ADT) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1C0QK0-0005Lq-00 for ; Thu, 26 Aug 2004 21:54:08 +0200 Received: from sp-260-1.net4.netcentrix.net ([4.21.254.118]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 26 Aug 2004 21:54:08 +0200 Received: from doug by sp-260-1.net4.netcentrix.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 26 Aug 2004 21:54:08 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: pgsql-performance@postgresql.org From: Doug McNaught Subject: Re: Anyone familiar with Apple Xserve RAID Date: Thu, 26 Aug 2004 15:54:04 -0400 Lines: 23 Message-ID: <87hdqpzndv.fsf@asmodeus.mcnaught.org> References: <1093468177.12331.424.camel@camel> <200408251422.08366.josh@agliodbs.com> <08139423-F6EB-11D8-ACDB-000393DB553C@bahn.de> <200408251649.02932.josh@agliodbs.com> <412E34B8.6000708@speedfc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: sp-260-1.net4.netcentrix.net User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/20.7 (gnu/linux) Cancel-Lock: sha1:kh7q2LzTKEdh2PlNnE3dZv6/uqM= 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: 200408/375 X-Sequence-Number: 8011 Kevin Barnard writes: > Actually you are both are right and wrong. The XRaid uses > FibreChannel to communicate to the host machine(s). The Raid > controller is a FibreChannel controller. After that there is a > FibreChannel to UltraATA conversion for each drive, separate ATA bus > for each drive. > What I am curious about is if this setup gets around ATA fsync > problems, where the drive reports the write before it is actually > performed. Good point. (a) The FC<->ATA unit hopefully has a battery-backed cache, which would make the whole thing more robust against power loss. (b) Since Apple is the vendor for the drive units, they can buy ATA drives that don't lie about cache flushes. Whether they do or not is definitely a question. ;) -Doug -- Let us cross over the river, and rest under the shade of the trees. --T. J. Jackson, 1863