X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 177713CAAC3 for ; Thu, 16 Dec 2004 14:26:50 +0000 (GMT) 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 89104-06 for ; Thu, 16 Dec 2004 14:26:28 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 548A73CAAA9 for ; Thu, 16 Dec 2004 14:26:31 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id iBGEQQ0X090003 for ; Thu, 16 Dec 2004 14:26:26 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id iBGE1AhI079714 for pgsql-admin@postgresql.org; Thu, 16 Dec 2004 14:01:10 GMT (envelope-from news) From: William Yu X-Newsgroups: pgsql.admin Subject: Re: Tyan Thunder MB for postgres server Date: Thu, 16 Dec 2004 05:59:48 -0800 Organization: Hub.Org Networking Services Lines: 22 Message-ID: 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> <007201c4e315$9074f960$7201a8c0@mst1x5r347kymb> <41C135BB.3030702@talisys.com> <000901c4e34a$a6770700$7201a8c0@mst1x5r347kymb> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en In-Reply-To: <000901c4e34a$a6770700$7201a8c0@mst1x5r347kymb> To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200412/161 X-Sequence-Number: 15747 Iain wrote: > 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. What they're saying is in the case of (AsB) m (CsD) -- if A fails, they no longer count B as part of the array and no longer part of the possible drives that can fail. Sorta like the "no one hears a tree fall, did it fall" scenario. I personally disagree with that theory. B is still part of the array. Pop in a new drive and the array is ready to start resync (CsD) --> (AsB). You still have a 1/3 chance in surviving another drive failure as long as B is the one that dies. Although now that I think about it, RAID10 is more resillient because the odds are survival after 1 failure is 2/3. In the case of (AmB) s (CmD), if A fails, you can survive C failing or D failing.