From: Joshua Marsh <icub3d@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: ERROR: could not read block
Date: Mon, 14 Nov 2005 17:02:24 -0700
Message-ID: <38242de90511141602v6a97e2a8r7992991f0b04577f@mail.gmail.com> (raw)
In-Reply-To: <1132011827.3582.18.camel@state.g2switchworks.com>
References: <4378C76502000025000006AE@gwmta.wicourts.gov>
<1132011827.3582.18.camel@state.g2switchworks.com>
On 11/14/05, Scott Marlowe <smarlowe@g2switchworks.com> wrote:
> If you were running on top of a RAID 1+0 or RAID 5 array, such an error
> would likely never have happened, since it would have been detected by
> the controller, and either the bad block would be mapped out or the
> drive would be kicked out of the array and you'd get a system alert
> telling you you had a bad drive in your array.
>
>
Except that he jus said he was running on a RAID5. True this problem would
be unlikely on a hardware controlled RAID5 configuration, but not
impossible.
Does the log file tell you anymore information?
Have you tried to rerun the query? If so, did you get similar results?
-Josh
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: icub3d@gmail.com
Subject: Re: ERROR: could not read block
In-Reply-To: <38242de90511141602v6a97e2a8r7992991f0b04577f@mail.gmail.com>
* 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