pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: L.Boldareva <pg@pierro.dds.nl>
Cc: pgsql-admin@postgresql.org
Subject: Re: How to recover when can't start database
Date: Fri, 01 Apr 2005 10:22:53 -0500
Message-ID: <6531.1112368973@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.58.0504011149340.17008@yafa.dds.nl>
References: <Pine.LNX.4.58.0504011149340.17008@yafa.dds.nl>

"L.Boldareva" <pg@pierro.dds.nl> writes:
> LOG:  database system was not properly shut down; automatic recovery in
> progress
> LOG:  redo starts at 5/6F000ABC
> PANIC:  btree_split_redo: lost left sibling
> LOG:  startup process (PID 5603) was terminated by signal 6

Hmm.  AFAICS that could only happen if a page split record is pointing
at an "original" page that's not there anymore; that is, the page is
past what the kernel says is the end of the file.  Exactly how did you
get into this state ... was there a system-level crash involved?  ISTM
this cannot happen unless the filesystem has dropped data.

You could probably get it to start by changing the "false" to "true"
in this call of XLogReadBuffer

	/* Left (original) sibling */
	buffer = XLogReadBuffer(false, reln, leftsib);
	if (!BufferIsValid(buffer))
		elog(PANIC, "btree_split_%s: lost left sibling", op);

in src/backend/access/nbtree/nbtxlog.c (it's line 261 in CVS tip,
possibly a little different in 8.0).  Let us know if that helps.

I'd be a bit suspicious of the contents of the index, if not the
whole database, so an immediate dump,reinitdb,reload might be your
most prudent course of action after you get it to start.

Plan B would be to wipe out the WAL log with pg_resetxlog.  This will
allow you to start but the odds of having corrupt data afterwards would
be about 100% ... you *must* dump and reload if you go that way.

			regards, tom lane



view thread (11+ messages)  latest in thread

Message-ID: <6531.1112368973@sss.pgh.pa.us>
Permalink:  ../6531.1112368973@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/6531.1112368973@sss.pgh.pa.us

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, pg@pierro.dds.nl
  Subject: Re: How to recover when can't start database
  In-Reply-To: <6531.1112368973@sss.pgh.pa.us>
  References: <Pine.LNX.4.58.0504011149340.17008@yafa.dds.nl> <6531.1112368973@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