From: | Joshua Marsh <icub3d(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: ERROR: could not read block |
Date: | 2005-11-15 00:02:24 |
Message-ID: | 38242de90511141602v6a97e2a8r7992991f0b04577f@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 11/14/05, Scott Marlowe <smarlowe(at)g2switchworks(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2005-11-15 00:19:16 | Re: ERROR: could not read block |
Previous Message | Scott Marlowe | 2005-11-14 23:43:47 | Re: ERROR: could not read block |