pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: William Yu <wyu@talisys.com>
To: pgsql-admin@postgresql.org
Subject: Re: Tyan Thunder MB for postgres server
Date: Wed, 15 Dec 2004 15:29:58 -0800
Message-ID: <cpqhgb$2bun$1@news.hub.org> (raw)
In-Reply-To: <004501c4e268$acbadca0$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>

Iain wrote:
> Upon further investigation, I think this the way to go, specificaly 
> I'llbe recommending the 320-2 as I plan to put the WAL and DB on 
> seperate channels and partitions (as opposed to to putting them on the 
> same logical partition split over the two channels).

SOmething to think about. Let's suppose a channel/cable completely dies. 
How would you protect against it? Split a logical mirror device over 2 
channels.

Another trick I've started doing with my MegaRAID setups is mirroring in 
hardware but striping in software. To do 100% hardware RAID-10 MegaRAID 
cards, all drives must have the same geometry. Not a big deal when 
you're first configuring a server but a few years down the line when a 
drive dies and you need a replacement, it can drive you up the wall. I 
had a set of IBM 36GBs that needed a replacement -- couldn't find any 
old stock so I decided to get the newest IBM (Hitachi) 36GBs -- NOT THE 
SAME GEOMETRY!@!@!#!$##

After learning that lesson, I did some testing with mirroring. LSI is 
much less stringent for mirroring. I was able to pair a Seagate + IBM 
and still get a valid mirror drive. I then use Linux software RAID to 
stripe 2 mirror volumes together.



view thread (16+ messages)  latest in thread

Message-ID: <cpqhgb$2bun$1@news.hub.org>
Permalink:  ../cpqhgb$2bun$1@news.hub.org/
Also on:    postgresql.org/message-id/cpqhgb$2bun$1@news.hub.org

 · 

reply

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: wyu@talisys.com
  Subject: Re: Tyan Thunder MB for postgres server
  In-Reply-To: <cpqhgb$2bun$1@news.hub.org>
  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>

* 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