Обсуждение: Most urgent

Поиск
Список
Период
Сортировка

Most urgent

От
ohp@pyrenet.fr
Дата:
My server just had a bad crash...
At reboot time, the pg_xlog filesystem didn't mount...
The I have those errors at startup...

is there anything  can do to recover?

Jan 27 13:24:11 server postgres[3469]: [3-1] LOG:  checkpoint record is at 7/B7668
Jan 27 13:24:11 server postgres[3469]: [4-1] LOG:  redo record is at 7/A08; undo record is at 0/0; shutdown FALSE
Jan 27 13:24:11 server postgres[3469]: [5-1] LOG:  next transaction ID: 21363395; next OID: 85839615
Jan 27 13:24:11 server postgres[3469]: [6-1] LOG:  database system was not properly shut down; automatic recovery in
progress
Jan 27 13:24:11 server postgres[3469]: [7-1] LOG:  redo starts at 7/A08
Jan 27 13:24:11 server postgres[3469]: [8-1] PANIC:  could not read block 222 of relation "79389213": Périphérique ou
adresseinexistants
 
Jan 27 13:24:11 server postgres[3467]: [2-1] LOG:  startup process (PID 3469) was terminated by signal 6
Jan 27 13:24:11 server postgres[3467]: [3-1] LOG:  aborting startup due to startup process failure
Jan 27 13:27:04 server postgres[3569]: [1-1] LOG:  could not bind IPv6 socket: Réseau inaccessible
Jan 27 13:27:04 server postgres[3569]: [1-2] HINT:  Is another postmaster already running on port 5432? If not, wait a
fewseconds and retry.
 
Jan 27 13:27:04 server postgres[3571]: [2-1] LOG:  database system was interrupted while in recovery at 2004-01-27
13:24:11MET
 
Jan 27 13:27:04 server postgres[3571]: [2-2] HINT:  This probably means that some data is corrupted and you will have
touse the last backup for recovery.
 
Jan 27 13:27:04 server postgres[3571]: [3-1] LOG:  checkpoint record is at 7/B7668
Jan 27 13:27:04 server postgres[3571]: [4-1] LOG:  redo record is at 7/A08; undo record is at 0/0; shutdown FALSE
Jan 27 13:27:04 server postgres[3571]: [5-1] LOG:  next transaction ID: 21363395; next OID: 85839615
Jan 27 13:27:04 server postgres[3571]: [6-1] LOG:  database system was not properly shut down; automatic recovery in
progress
Jan 27 13:27:04 server postgres[3571]: [7-1] LOG:  redo starts at 7/A08
Jan 27 13:27:04 server postgres[3571]: [8-1] PANIC:  could not read block 222 of relation "79389213": Périphérique ou
adresseinexistants
 
Jan 27 13:27:04 server postgres[3569]: [2-1] LOG:  startup process (PID 3571) was terminated by signal 6
Jan 27 13:27:04 server postgres[3569]: [3-1] LOG:  aborting startup due to startup process failure

-- 
Olivier PRENANT                    Tel: +33-5-61-50-97-00 (Work)
6, Chemin d'Harraud Turrou           +33-5-61-50-97-01 (Fax)
31190 AUTERIVE                       +33-6-07-63-80-64 (GSM)
FRANCE                          Email: ohp@pyrenet.fr
------------------------------------------------------------------------------
Make your life a dream, make your dream a reality. (St Exupery)


Re: Most urgent

От
Tom Lane
Дата:
ohp@pyrenet.fr writes:
> My server just had a bad crash...
> At reboot time, the pg_xlog filesystem didn't mount...

So mount it...

If you're trying to say that the xlog is irretrievably hosed, then see
pg_resetxlog, and be prepared to spend some time checking to see if
anything got corrupted.  But first try to get your xlog back.
        regards, tom lane


Re: Most urgent

От
ohp@pyrenet.fr
Дата:
On Tue, 27 Jan 2004, Tom Lane wrote:

> Date: Tue, 27 Jan 2004 12:02:04 -0500
> From: Tom Lane <tgl@sss.pgh.pa.us>
> To: ohp@pyrenet.fr
> Cc: pgsql-hackers list <pgsql-hackers@postgresql.org>
> Subject: Re: [HACKERS] Most urgent
>
> ohp@pyrenet.fr writes:
> > My server just had a bad crash...
> > At reboot time, the pg_xlog filesystem didn't mount...
>
> So mount it...
Of course I did...
As you can see from the logs I sent, it didn't help
>
> If you're trying to say that the xlog is irretrievably hosed, then see
> pg_resetxlog, and be prepared to spend some time checking to see if
> anything got corrupted.  But first try to get your xlog back.
>
Well, apparently, the fs itself was badly corrupted (should'nt happen, I'm
using fsync + ODM mirroring)
So I ended up reinstalling every thing and restart all db from backups.

BTW, I still have statistics buffer full message (never very far from a
reclycling of log file) maybe it's just a conincidence

>             regards, tom lane
>

-- 
Olivier PRENANT                    Tel: +33-5-61-50-97-00 (Work)
6, Chemin d'Harraud Turrou           +33-5-61-50-97-01 (Fax)
31190 AUTERIVE                       +33-6-07-63-80-64 (GSM)
FRANCE                          Email: ohp@pyrenet.fr
------------------------------------------------------------------------------
Make your life a dream, make your dream a reality. (St Exupery)