Re: Recovery Data Cant Be!!! - Mailing list pgsql-general
From | Edwin Quijada |
---|---|
Subject | Re: Recovery Data Cant Be!!! |
Date | |
Msg-id | BAY1-F99wAeRaNgEpTX00013ba6@hotmail.com Whole thread Raw |
In response to | Recovery Data Cant Be!!! ("Edwin Quijada" <listas_quijada@hotmail.com>) |
List | pgsql-general |
This is the way to do that? ./pgfsck -D /usr/local/pgsql/data -da union_seguros > /var/lib/pgsql/bak_union What is the correct setting to never do that? What is a solid storage subsystem? fsync=false ? write cache enabled? Can you explain me this? Postgres I use IDE disk *-------------------------------------------------------* *-Edwin Quijada *-Developer DataBase *-JQ Microsistemas *-809-747-2787 * " Si deseas lograr cosas excepcionales debes de hacer cosas fuera de lo comun" *-------------------------------------------------------* >From: "scott.marlowe" <scott.marlowe@ihs.com> >To: Edwin Quijada <listas_quijada@hotmail.com> >CC: <pgsql-general@postgresql.org> >Subject: Re: [GENERAL] Recovery Data Cant Be!!! >Date: Fri, 7 Nov 2003 13:29:57 -0700 (MST) > >You're likely looking for pgfsck: > >http://svana.org/kleptog/pgsql/pgfsck.html > >Strong medicine, please backup your $PGDATA directory before playing >there, as you might wind up breaking things. > >What's the exact error message in your logs when the database won't start >up? > >The problem you're seeing is common when running on IDE drives with write >cache enabled, or with fsync=false on IDE with write cache disabled or >SCSI. On a solid storage subsystem, postgresql is close to >indestrubtable, i.e. you can crank up 500 simo transactions, pull the >plug, and the database will come right back up. That's how we test our >servers to make sure that the WAL and such is working properly. > >On Fri, 7 Nov 2003, Edwin Quijada wrote: > > > Hi!! > > There is an app to recover data for postgres after inapropiate server > > shutdown or power electrical down? > > I have a great problem. My system go down inapropiate and now my server > > doesnt up. > > What 's up with my data? > > I lost my data? > > I dont believe that a robust database like postgres is so weak for power > > down and understand that can go down electrical power but fail 2 ups. > > > > If somebody has any idea to help me this is the log file > > > > The server must be started under an unprivileged user id to prevent > > a possible system security compromise. See the documentation for > > more information on how to properly start the server. > > > > LOG: database system was interrupted at 2003-11-07 10:54:32 CET > > LOG: checkpoint record is at 1/34600318 > > LOG: redo record is at 1/34600318; undo record is at 0/0; shutdown >FALSE > > LOG: next transaction id: 6326695; next oid: 5776573 > > LOG: database system was not properly shut down; automatic recovery in > > progress > > LOG: redo starts at 1/34600358 > > PANIC: Invalid page header in block 8805 of 17097 > > LOG: startup process (pid 1327) was terminated by signal 6 > > LOG: aborting startup due to startup process failure > > LOG: database system was interrupted being in recovery at 2003-11-07 > > 23:33:19 CET > > 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 1/34600318 > > LOG: redo record is at 1/34600318; undo record is at 0/0; shutdown >FALSE > > LOG: next transaction id: 6326695; next oid: 5776573 > > LOG: database system was not properly shut down; automatic recovery in > > progress > > LOG: redo starts at 1/34600358 > > PANIC: Invalid page header in block 8805 of 17097 > > LOG: startup process (pid 1354) was terminated by signal 6 > > LOG: aborting startup due to startup process failure > > LOG: database system was interrupted being in recovery at 2003-11-07 > > 23:35:34 CET > > 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 1/34600318 > > LOG: redo record is at 1/34600318; undo record is at 0/0; shutdown >FALSE > > LOG: next transaction id: 6326695; next oid: 5776573 > > LOG: database system was not properly shut down; automatic recovery in > > progress > > LOG: redo starts at 1/34600358 > > PANIC: Invalid page header in block 8805 of 17097 > > LOG: startup process (pid 1090) was terminated by signal 6 > > LOG: aborting startup due to startup process failure > > LOG: database system was interrupted being in recovery at 2003-11-07 > > 23:40:47 CET > > 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 1/34600318 > > LOG: redo record is at 1/34600318; undo record is at 0/0; shutdown >FALSE > > LOG: next transaction id: 6326695; next oid: 5776573 > > LOG: database system was not properly shut down; automatic recovery in > > progress > > LOG: redo starts at 1/34600358 > > PANIC: Invalid page header in block 8805 of 17097 > > LOG: startup process (pid 1196) was terminated by signal 6 > > LOG: aborting startup due to startup process failure > > LOG: database system was interrupted being in recovery at 2003-11-07 > > 23:46:13 CET > > 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 1/34600318 > > LOG: redo record is at 1/34600318; undo record is at 0/0; shutdown >FALSE > > LOG: next transaction id: 6326695; next oid: 5776573 > > LOG: database system was not properly shut down; automatic recovery in > > progress > > LOG: redo starts at 1/34600358 > > PANIC: Invalid page header in block 8805 of 17097 > > LOG: startup process (pid 1531) was terminated by signal 6 > > LOG: aborting startup due to startup process failure > > > > > > > > > > *-------------------------------------------------------* > > *-Edwin Quijada > > *-Developer DataBase > > *-JQ Microsistemas > > *-809-747-2787 > > * " Si deseas lograr cosas excepcionales debes de hacer cosas fuera de >lo > > comun" > > *-------------------------------------------------------* > > > > _________________________________________________________________ > > >From Beethoven to the Rolling Stones, your favorite music is always >playing > > on MSN Radio Plus. No ads, no talk. Trial month FREE! > > http://join.msn.com/?page=offers/premiumradio > > > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 3: if posting/reading through Usenet, please send an appropriate > > subscribe-nomail command to majordomo@postgresql.org so that your > > message can get through to the mailing list cleanly > > > > > _________________________________________________________________ Is your computer infected with a virus? Find out with a FREE computer virus scan from McAfee. Take the FreeScan now! http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
pgsql-general by date: