pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: pgsql-admin@postgresql.org
Subject: Re: RESOLVED: Explained by known hardware failures, or keep looking?
Date: Wed, 20 Jun 2007 09:26:32 -0500
Message-ID: <4678F2C7.EE98.0025.0@wicourts.gov> (raw)
In-Reply-To: <4713.1182198324@sss.pgh.pa.us>
References: <467699B7.EE98.0025.0@wicourts.gov>
	<467699B7.EE98.0025.0@wicourts.gov>
	<4713.1182198324@sss.pgh.pa.us>

Thanks, all.  Just an FYI to wrap up the thread.

>>> On Mon, Jun 18, 2007 at  3:25 PM, in message <4713.1182198324@sss.pgh.pa.us>,
Tom Lane <tgl@sss.pgh.pa.us> wrote: 
> "Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
>> I'm suspicious that either the controller
>> didn't persist dirty pages in the June 14th failure
> 
> That's what it looks like to me --- it's hard to tell if the hardware or
> the filesystem is at fault, but one way or another some pages that were
> supposedly securely down on disk were wiped to zeroes.  You should
> probably review whether the hardware is correctly reporting write-complete.
 
The hardware tech found many problems with this box.  I may just give it
a heavy update load and pull both plugs to see if it comes up clean now.
 
The following was done:
 
Replaced 2 failed drives
Controller firmware updated
SCSI micro code updated
Performed Yast Online updates
Connected second power supply
 
Our newer boxes have monitoring software which alerts us before a box
gets into this bad a state.
 
-Kevin
 





Message-ID: <4678F2C7.EE98.0025.0@wicourts.gov>
Permalink:  ../4678F2C7.EE98.0025.0@wicourts.gov/
Also on:    postgresql.org/message-id/4678F2C7.EE98.0025.0@wicourts.gov

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: Kevin.Grittner@wicourts.gov
  Subject: Re: RESOLVED: Explained by known hardware failures, or keep looking?
  In-Reply-To: <4678F2C7.EE98.0025.0@wicourts.gov>

* 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