Re: [ADMIN] PANIC: unable to locate a valid checkpoint record

From: Ganesan R <rganesan(at)myrealbox(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [ADMIN] PANIC: unable to locate a valid checkpoint record
Date: 2003-02-21 04:48:00
Message-ID: 20030221044800.GA5899@andiamo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-bugs

On Thu, Feb 20, 2003 at 11:07:55PM -0500, Tom Lane wrote:
> Ganesan R <rganesan(at)myrealbox(dot)com> writes:
> > I am using 7.3.2. postmaster prints this on starting up:
>
> > LOG: ReadRecord: bad resource manager data checksum in record at 0/E42144
>
> > pg_resetxlog is able to recover from the problem; but I am concerned because
> > I can reproduce the scenario very easily.
>
> You should definitely be concerned :-(. It sounds like the CRC code
> isn't working at all on your platform. What is your platform --- what
> hardware, what OS, which C compiler? How did you configure and install
> Postgres?
>

Hi,

We've able recreate the problem on another platform; this time a
DELL PowerEdge 1650. See
http://www.dell.com/us/en/esg/topics/esg_pedge_rackmain_servers_1_pedge_1650.htm
The configuration is pretty much identical (Single Pentium III 1133MHz CPU,
dual mirrored SCSI drives, Redhat 7.3 running kernel 2.4.18). Please let me
know if you need additional information. Thank you.

Ganesan

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2003-02-21 05:29:48 Re: [ADMIN] PANIC: unable to locate a valid checkpoint record
Previous Message Ganesan R 2003-02-21 04:29:42 Re: PANIC: unable to locate a valid checkpoint record

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2003-02-21 05:29:48 Re: [ADMIN] PANIC: unable to locate a valid checkpoint record
Previous Message Ganesan R 2003-02-21 04:29:42 Re: PANIC: unable to locate a valid checkpoint record