From: Alan Stange <stange@rentec.com>
To: Doug McNaught <doug@mcnaught.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Anyone familiar with Apple Xserve RAID
Date: Thu, 26 Aug 2004 16:01:15 -0400
Message-ID: <412E418B.3070103@rentec.com> (raw)
In-Reply-To: <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>
<87hdqpzndv.fsf@asmodeus.mcnaught.org>
Doug McNaught wrote:
>Kevin Barnard <kbarnard@speedfc.com> 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. ;)
>
>
FYI: http://developer.apple.com/technotes/tn/pdf/tn1040.pdf a tech
note on write cache flushing.
A bit dated now, but perhaps some other tech note from Apple has more
recent information.
-- Alan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: stange@rentec.com, doug@mcnaught.org
Subject: Re: Anyone familiar with Apple Xserve RAID
In-Reply-To: <412E418B.3070103@rentec.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox