RE: PANIC: No levanta Postgres

Alvaro Herrera wrote:
> On Fri, Apr 29, 2005 at 06:29:03PM -0600, mmiranda(at)americatel(dot)com(dot)sv
> wrote:
>> 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
>
> Perdona mi ignorancia, el storage es separado del servidor? Es decir,
> quedo encendido cuando el servidor se apago?

Si , esta separado del servidor

>
> Tienes alguna especie de cluster de servidores que usen espacio
> compartido de PGDATA en ese storage?
>
> Que version de Postgres?

Efectivamente, es un cluster con heartbeat, pero solamente uno tiene montada
la particion data y corriendo postgres, heartbeat se encarga de reiniciar el
servicio y levantar los servicios en el otro servidor,

Habra posibilidades de levantarlo, porque sino creo que estoy perdiendo
tiempo valioso que pudiera aprovechar para reinstalar todo otra vez, a mi
me gustaria no tener que hacerlo

Migue