Hi,
we have had similar postgres problems in the past.
Please have a look at Bug 3484.
We didn't resolve the problems metioned in bug 3484. The other postgres developers also thought, that there are
hardware
problems.
So our customer bought a new server with diffrent hardware configuration ( ... and NEW hardware drives ... ).
The error today encountered on the new machine. Just running under heavy load since two days.
We ran two file checks. One normal with no error result.
One deep scan (e2fsck -fcn) searching for corrupted blocks. No error was reported.
It really looks unlikely having a hardware problem now.
Here are some details about the servers:
*NEW* server:
postgres 8.3.5
SUSE 10.3
Kernel 2.6.22.19-0.1-default
Supermicro-Mainboard + 2x AMD Opteron Dual Core 2218 2,60 GHz
4x 1024MB ECC Registered DDR2 Ram ATP
3Ware 9650 4x SATA
*OLD* server:
postgres 8.3.5
SUSE 10.0
Kernel 2.6.22.6-smp
Intel-Mainboard + 2x Intel XEON 2,80 GHz 2MB FSB800
4x 1024MB ECC Registered DDR2 RAM
3Ware Raid Controller 9500S-4
Regards,
A. Nitzschke
Craig Ringer schrieb:
> Alexandra Nitzschke wrote:
>> Hi,
>>
>> we encountered the following error while inserting a record into a table:
>>
>> org.postgresql.util.PSQLException: ERROR: could not read block 77 of
>> relation 1663/16385/388818775: read only 0 of 8192 bytes
>
> This is probably a problem with your disk or filesystem. Have you
> checked your disks and file system, checked your system logs for disk
> errors, made sure your RAID array is in good condition, etc?
>
> You should be able to fix it by REINDEXing the problem index. You can
> find out which index it is from pg_catalog, though if you just REINDEX
> the table(s) being operated on by the query that should work too.
>
> Consider making a copy of your database and your log files before you
> REINDEX in case one of the developers thinks it might actually be caused
> by a PostgreSQL bug and wants to have a look.
>
> --
> Craig Ringer
>
>