pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: anil maran <anilmrn@yahoo.com>
To: pgsql-admin@postgresql.org
Subject: Fw: postgres database crash
Date: Tue, 21 Nov 2006 16:29:42 -0800 (PST)
Message-ID: <20061122002942.44451.qmail@web55214.mail.re4.yahoo.com> (raw)

Hi
CRON job running vacuum on a database and pg_ctl stop -m fast got called

Now I m unable to run the database, the following is the error when I run pg_ctl -D /work/database start
LOG:  logger shutting down

on running 
tail -n 30 postgresql-Mon.log 
LOG:  database system was not properly shut down; automatic recovery in progress
LOG:  redo starts at 8A/8F00833C
PANIC:  block 1100 unfound
LOG:  startup process (PID 31612) was terminated by signal 6 
LOG:  aborting startup due to startup process failure
LOG:  logger shutting down
LOG:  database system was interrupted while in recovery at 2006-11-20 16:56:18 PST
HINT:  This probably means that some data is corrupted and you will have to use the last backup for recovery. 
LOG:  checkpoint record is at 8A/8F01D6D4
LOG:  redo record is at 8A/8F00833C; undo record is at 0/0; shutdown FALSE
LOG:  next transaction ID: 32782967; next OID: 2499839
LOG:  next MultiXactId: 972; next MultiXactOffset: 2099 
LOG:  database system was not properly shut down; automatic recovery in progress
LOG:  redo starts at 8A/8F00833C
PANIC:  block 1100 unfound
LOG:  startup process (PID 31846) was terminated by signal 6
LOG:  aborting startup due to startup process failure 
LOG:  logger shutting down
LOG:  database system was interrupted while in recovery at 2006-11-20 17:12:21 PST
HINT:  This probably means that some data is corrupted and you will have to use the last backup for recovery. 
LOG:  checkpoint record is at 8A/8F01D6D4
LOG:  redo record is at 8A/8F00833C; undo record is at 0/0; shutdown FALSE
LOG:  next transaction ID: 32782967; next OID: 2499839
LOG:  next MultiXactId: 972; next MultiXactOffset: 2099 
LOG:  database system was not properly shut down; automatic recovery in progress
LOG:  redo starts at 8A/8F00833C
PANIC:  block 1100 unfound
LOG:  startup process (PID 32000) was terminated by signal 6
LOG:  aborting startup due to startup process failure 
LOG:  logger shutting down

pg_controldata 
pg_control version number:            812
Catalog version number:               200510211
Database system identifier:           4952196794948500735 
Database cluster state:               in recovery
pg_control last modified:             Mon 20 Nov 2006 05:14:36 PM PST
Current log file ID:                  138
Next log file segment:                170
Latest checkpoint location:           8A/8F01D6D4 
Prior checkpoint location:            8A/8C01924C
Latest checkpoint's REDO location:    8A/8F00833C
Latest checkpoint's UNDO location:    0/0
Latest checkpoint's TimeLineID:       1
Latest checkpoint's NextXID:          32782967 
Latest checkpoint's NextOID:          2499839
Latest checkpoint's NextMultiXactId:  972
Latest checkpoint's NextMultiOffset:  2099
Time of latest checkpoint:            Mon 20 Nov 2006 12:53:56 PM PST
Maximum data alignment:               4 
Database block size:                  8192
Blocks per segment of large relation: 131072
Bytes per WAL segment:                16777216
Maximum length of identifiers:        64
Maximum columns in an index:          32 
Date/time type storage:               floating-point numbers
Maximum length of locale name:        128
LC_COLLATE:                            en_US.UTF-8
LC_CTYPE:                              en_US.UTF-8


I tried running pg_resetxlog everything got lost, so restoring the copied database folder

I got pointers to looking at pg_filedump and I could not find out how to specify options to filedump
Please help me out
my data bases is like 1gigabyte, panicking
thanks

 
Anil


 
____________________________________________________________________________________
Sponsored Link

Mortgage rates near 39yr lows. $510k for $1,698/mo. 
Calculate new payment! www.LowerMyBills.com/lre

view thread (2+ messages)  latest in thread

Message-ID: <20061122002942.44451.qmail@web55214.mail.re4.yahoo.com>
Permalink:  ../20061122002942.44451.qmail@web55214.mail.re4.yahoo.com/
Also on:    postgresql.org/message-id/20061122002942.44451.qmail@web55214.mail.re4.yahoo.com

 · 

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: anilmrn@yahoo.com
  Subject: Re: Fw: postgres database crash
  In-Reply-To: <20061122002942.44451.qmail@web55214.mail.re4.yahoo.com>
  References: <20061122002942.44451.qmail@web55214.mail.re4.yahoo.com>

* 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