Skip navigation links

MySQL Forums :: InnoDB :: Recovering Corrupt ibdata1 files


Advanced Search

Re: Recovering Corrupt ibdata1 files
Posted by: Marc Perkel ()
Date: June 28, 2007 03:34PM

Here's the log on startup.

070628 14:29:02 mysqld ended

070628 14:29:57 mysqld started
070628 14:29:57 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
070628 14:29:57 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 1310533163.
InnoDB: Doing recovery: scanned up to log sequence number 0 1310533163
InnoDB: Page directory corruption: supremum not pointed to
070628 14:30:00 InnoDB: Page dump in ascii and hex (16384 bytes):
070628 14:30:00 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page directory corruption: supremum not pointed to
070628 14:30:00 InnoDB: Page dump in ascii and hex (16384 bytes):
070628 14:30:00 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
070628 14:30:00InnoDB: Error: trying to access a stray pointer 0x80002aaaad083ff8
InnoDB: buf pool start is at 0x2aaaad074000, end at 0x2aaaad874000
InnoDB: Probable reason is database corruption or memory
InnoDB: corruption. If this happens in an InnoDB database recovery, see
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: how to force recovery.
070628 14:30:00InnoDB: Assertion failure in thread 46912496244656 in file ./../include/buf0buf.ic line 259
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=0
read_buffer_size=8384512
max_used_connections=0
max_connections=4000
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 65519968 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=(nil)
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
frame pointer is NULL, did you compile with
-fomit-frame-pointer? Aborting backtrace!
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
070628 14:30:00 mysqld ended

Options: ReplyQuote


Subject Views Written By Posted
Recovering Corrupt ibdata1 files 15384 Marc Perkel 06/28/2007 03:27PM
Re: Recovering Corrupt ibdata1 files 13404 Marc Perkel 06/28/2007 03:34PM
Re: Recovering Corrupt ibdata1 files 9008 KimSeong Loh 06/29/2007 04:42PM
Re: Recovering Corrupt ibdata1 files 8917 paz paz 01/02/2008 12:32AM
Re: Recovering Corrupt ibdata1 files 12658 Frank Flynn 01/18/2008 07:59PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.