From: | mmiranda(at)americatel(dot)com(dot)sv |
---|---|
To: | alvherre(at)dcc(dot)uchile(dot)cl, mmiranda(at)americatel(dot)com(dot)sv |
Cc: | pgsql-es-ayuda(at)postgresql(dot)org |
Subject: | RE: PANIC: No levanta Postgres |
Date: | 2005-04-30 00:29:03 |
Message-ID: | 76E0DAA32C39D711B6EC0002B364A6FA0445C3FF@amsal01exc01.americatel.com.sv |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-es-ayuda |
Alvaro Herrera wrote:
> On Fri, Apr 29, 2005 at 02:19:26PM -0600, mmiranda(at)americatel(dot)com(dot)sv
> wrote:
>
>> LOG: database system was interrupted being in recovery at
>> 2005-04-29 14:10:43 CST This probably means that some data
>> blocks are corrupted and you will have to use the last
>> backup for recovery.
>> LOG: checkpoint record is at F1/A0A4E05C
>> LOG: redo record is at F1/A0A4E05C; undo record is at 0/0; shutdown
>> TRUE LOG: next transaction id: 98967076; next oid: 151578857
>> LOG: database system was not properly shut down; automatic recovery
>> in progress LOG: redo starts at F1/A0A4E09C
>> PANIC: Invalid page header in block 68122 of 17006
>> LOG: startup process (pid 1959) was terminated by signal 6
>> LOG: aborting startup due to startup process failure
>
> Que clase de discos? (ide, scsi, raid?) Que sistema operativo? Que
> tipo de filesystem? Tienes fsync off en posgresql.conf?
Es un array HP MSA500 discos scsi 10k, raid 5, redhat 7.3, fsync on (opcion
por defecto) en postgresql.conf
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2005-04-30 00:30:49 | Re: Consulta sobre el vacuum |
Previous Message | Camilo Ismael Felipe Panadeiros | 2005-04-29 22:45:58 | duda sobre php y postgres |