From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
Cc: | "Luke Lonergan" <llonergan(at)greenplum(dot)com>, "Rajesh Kumar Mallah" <mallah(dot)rajesh(at)gmail(dot)com>, <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: setting up raid10 with more than 4 drives |
Date: | 2007-05-30 12:08:25 |
Message-ID: | 874plubjk6.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
"Jonah H. Harris" <jonah(dot)harris(at)gmail(dot)com> writes:
> On 5/29/07, Luke Lonergan <llonergan(at)greenplum(dot)com> wrote:
>> AFAIK you can't RAID1 more than two drives, so the above doesn't make sense
>> to me.
Sure you can. In fact it's a very common backup strategy. You build a
three-way mirror and then when it comes time to back it up you break it into a
two-way mirror and back up the orphaned array at your leisure. When it's done
you re-add it and rebuild the degraded array. Good raid controllers can
rebuild the array at low priority squeezing in the reads in idle cycles.
I don't think you normally do it for performance though since there's more to
be gained by using larger stripes. In theory you should get the same boost on
reads as widening your stripes but of course you get no benefit on writes. And
I'm not sure raid controllers optimize raid1 accesses well in practice either.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Luke Lonergan | 2007-05-30 14:06:54 | Re: setting up raid10 with more than 4 drives |
Previous Message | Stephen Frost | 2007-05-30 10:42:36 | Re: setting up raid10 with more than 4 drives |