Re: 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: Ganesan R <rganesan(at)myrealbox(dot)com>, pgsql-bugs(at)postgresql(dot)org, pgsql-admin(at)postgresql(dot)org
Subject: Re: PANIC: unable to locate a valid checkpoint record
Date: 2003-02-21 04:29:42
Message-ID: 20030221042942.GA5785@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?

The hardware is an IBM xSeries 340 with a single Xeon Pentium IV 2.40GHz
processor with dual mirrored SCSI disks. The OS is Redhat Linux 7.3 with a
Linux 2.4.18 SMP kernel (the CPU supports hyperthreading). PostgreSQL
binaries were precompiled. PostgreSQL 7.2.1 version is a redhat build
shippping with Redhat Linux 7.3. PostgresQL 7.2.4 and 7.3.2 binaries were
directly downloaded from the ftp mirrors.

Please let me know if you need additional information.

Ganesan

In response to

Browse pgsql-admin by date

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

Browse pgsql-bugs by date

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