X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id 3B0ECDA3E6
	for <pgsql-admin-postgresql.org@localhost.postgresql.org>;
	Mon, 14 Nov 2005 20:02:24 -0400 (AST)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 30498-10
	for <pgsql-admin-postgresql.org@localhost.postgresql.org>;
	Tue, 15 Nov 2005 00:02:19 +0000 (GMT)
X-Greylist: domain auto-whitelisted by SQLgrey-
Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.198])
	by svr1.postgresql.org (Postfix) with ESMTP id 6C358D6D1D
	for <pgsql-admin@postgresql.org>; Mon, 14 Nov 2005 20:02:21 -0400 (AST)
Received: by zproxy.gmail.com with SMTP id o37so1241958nzf
	for <pgsql-admin@postgresql.org>; Mon, 14 Nov 2005 16:02:24 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
	b=dVmT/9kks+DJNwzx7W1BlPbmGx4YsLL8TCwch8J3L9VZDrNaQyPtpQU2QeOH0EQvEx1U2Xxpm6tiRT1mT9K7uaZCENfUWcOkQ/Pgho9xI+/YCPs5o/Ulx0FAFnMzlx3x8HtMi2NolmL05UUBlZY3srs1RGpjWMwQQt9gCsSrP7o=
Received: by 10.65.218.2 with SMTP id v2mr6301043qbq;
	Mon, 14 Nov 2005 16:02:24 -0800 (PST)
Received: by 10.64.243.11 with HTTP; Mon, 14 Nov 2005 16:02:24 -0800 (PST)
Message-ID: <38242de90511141602v6a97e2a8r7992991f0b04577f@mail.gmail.com>
Date: Mon, 14 Nov 2005 17:02:24 -0700
From: Joshua Marsh <icub3d@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: ERROR: could not read block
In-Reply-To: <1132011827.3582.18.camel@state.g2switchworks.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_7693_2486813.1132012944128"
References: <4378C76502000025000006AE@gwmta.wicourts.gov>
	<1132011827.3582.18.camel@state.g2switchworks.com>
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0.001 required=5 tests=[HTML_MESSAGE=0.001]
X-Spam-Score: 0.001
X-Spam-Level: 
X-Archive-Number: 200511/160
X-Sequence-Number: 19533

------=_Part_7693_2486813.1132012944128
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

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

------=_Part_7693_2486813.1132012944128
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<br><br><div><span class=3D"gmail_quote">On 11/14/05, <b class=3D"gmail_sen=
dername">Scott Marlowe</b> &lt;<a href=3D"mailto:smarlowe@g2switchworks.com=
">smarlowe@g2switchworks.com</a>&gt; wrote:</span><br><blockquote class=3D"=
gmail_quote" style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0p=
t 0pt 0pt 0.8ex; padding-left: 1ex;">
If you were running on top of a RAID 1+0 or RAID 5 array, such an error<br>=
would likely never have happened, since it would have been detected by<br>t=
he controller, and either the bad block would be mapped out or the<br>drive=
 would be kicked out of the array and you'd get a system alert
<br>telling you you had a bad drive in your array.<br><br></blockquote></di=
v><br clear=3D"all">Except
that he jus said he was running on a RAID5.&nbsp; True this problem
would be unlikely on a hardware controlled RAID5 configuration, but not
impossible.&nbsp; <br>
<br>
Does the log file tell you anymore information?&nbsp; <br>
<br>
Have you tried to rerun the query?&nbsp; If so, did you get similar results=
?<br>
<br>
-Josh<br>

------=_Part_7693_2486813.1132012944128--