From: Tom Lane <tgl@sss.pgh.pa.us>
To: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: pgsql-admin@postgresql.org
Subject: Re: ERROR: could not read block
Date: Mon, 14 Nov 2005 19:43:56 -0500
Message-ID: <4636.1132015436@sss.pgh.pa.us> (raw)
In-Reply-To: <1132011827.3582.18.camel@state.g2switchworks.com>
References: <4378C76502000025000006AE@gwmta.wicourts.gov>
<1132011827.3582.18.camel@state.g2switchworks.com>
Scott Marlowe <smarlowe@g2switchworks.com> writes:
> On Mon, 2005-11-14 at 17:20, Kevin Grittner wrote:
>> ERROR: could not read block 649847 of relation 1663/16385/16483:
>> Invalid argument
> When a block is unreadable, this means that the OS is experiencing a
> read error from the hard drive.
I'd believe that explanation if the errno were EIO (I/O error), but
EINVAL isn't really a very sane error number to return for a hardware
failure. It'd be useful to find out what Windows error code is actually
being returned by the operating system. I seem to recall that we've
noted some poorly chosen Windows->errno translations before, so maybe
this is another one ... but all we can really say at the moment is
"that shouldn't be happening".
regards, tom lane
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: tgl@sss.pgh.pa.us, smarlowe@g2switchworks.com, Kevin.Grittner@wicourts.gov
Subject: Re: ERROR: could not read block
In-Reply-To: <4636.1132015436@sss.pgh.pa.us>
* 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