From: Iain <iain@mst.co.jp>
To: William Yu <wyu@talisys.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Tyan Thunder MB for postgres server
Date: Thu, 16 Dec 2004 17:38:39 +0900
Message-ID: <000901c4e34a$a6770700$7201a8c0@mst1x5r347kymb> (raw)
References: <021a01c4e0dc$774d0620$7201a8c0@mst1x5r347kymb>
<41BDB10A.6000200@did-it.com>
<00bf01c4e17c$db69e100$7201a8c0@mst1x5r347kymb>
<1103038201.22049.14.camel@state.g2switchworks.com>
<000b01c4e24a$43deaae0$7201a8c0@mst1x5r347kymb>
<41BFB085.6010102@talisys.com>
<004501c4e268$acbadca0$7201a8c0@mst1x5r347kymb>
<cpqhgb$2bun$1@news.hub.org>
<007201c4e315$9074f960$7201a8c0@mst1x5r347kymb>
<41C135BB.3030702@talisys.com>
Thanks again for your valuable input William.
> I'm not sure why people say one is better than the other. Both will
> survive the loss of 2 drives -- they're just different drives.
> RAID 0+1: A(1m1) s B(1m1) <-- any drive on A and any drive on B
> RAID 10: A(1s1) m B(1s1) <-- both drives on A or both drives on B
I'm wondering if we have a terminology problem here. As I understand it the
configs are the reverse of what you said. I only checked www.bytepile.com:
so I hope they're not wrong! I quote:
"RAID 0+1 is implemented as a mirrored array whose segments are RAID 0"
"RAID 10 is implemented as a striped array whose segments are RAID 1"
This is the quote that interested me "RAID 0+1 is NOT to be confused with
RAID 10. A single drive failure will cause the whole array to become, in
essence, a RAID Level 0 array" and "Under certain circumstances, RAID 10
array can sustain multiple simultaneous drive failures".
As bytepile has it, failure of 1 disk in 0+1 leaves you with just RAID 0 so
one more failure on the other pair and your data is gone. On the other hand,
failure of 1 disk in raid 10 leaves you with a working raid 1 that can
sustain a second failure.
> Either way, I think you can do both across 2 channels to be redundant for
> a channel/cable failing.
>
> RAID 0+1: C1-m-C2 s C1-m-C2
> RAID 10: C1-s-C1 m C2-s-C2
Gaaa! I'll have to ponder that one. C1-m-C2 s C1-m-C2 sounds good in theory.
Presumably to be practical it would require hardware and maybe software
support, so the machine continues to operate despite the failure (and
hopefully tells you about it). It would interesting to test it anyway.
> Always get more space than you need if you can afford it because it's a
> pain in the ass adding more disk space. Especially on the boot drives.
Very true.
> Doing a google search for "hot swap cpu", I see they've added something
> into Linux but you'd still need hardware support.
I'm sure that if the Tyan board had that support they'd be making a fuss of
it :-) I'll have a look for "hot swap cpu" too though, just for interests
sake.
High redundancy is becoming more accessible I think, but it still takes a
lot more money than your average PC server motherboard costs to get it ;-)
something to look forward to anyway.
Cheers,
Iain
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: iain@mst.co.jp, wyu@talisys.com
Subject: Re: Tyan Thunder MB for postgres server
In-Reply-To: <000901c4e34a$a6770700$7201a8c0@mst1x5r347kymb>
References: <021a01c4e0dc$774d0620$7201a8c0@mst1x5r347kymb> <41BDB10A.6000200@did-it.com> <00bf01c4e17c$db69e100$7201a8c0@mst1x5r347kymb> <1103038201.22049.14.camel@state.g2switchworks.com> <000b01c4e24a$43deaae0$7201a8c0@mst1x5r347kymb> <41BFB085.6010102@talisys.com> <004501c4e268$acbadca0$7201a8c0@mst1x5r347kymb> <cpqhgb$2bun$1@news.hub.org> <007201c4e315$9074f960$7201a8c0@mst1x5r347kymb> <41C135BB.3030702@talisys.com> <000901c4e34a$a6770700$7201a8c0@mst1x5r347kymb>
* 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