We had a power outage, and since that time we cannot start the mysql server. When I look at the logs, it seems it is hitting an assertion in the InnoDB recovery. I cannot seem to get past this point and would very much like to at least be able to recover some of my databases. Is there any way to bypass recovery? Or is there some way to get around or fix this issue properly?
Log file/stack trace follows:
InnoDB: Log scan progressed past the checkpoint lsn 2 1069785400
090518 17:30:38 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...
InnoDB: Error: tried to read 16384 bytes at offset 0 107266048.
InnoDB: Was only able to read 4096.
InnoDB: Fatal error: cannot read from file. OS error number 17.
090518 17:30:53InnoDB: Assertion failure in thread 3082966720 in file os0file.c line 2211
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.
090518 17:30:53 - 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=131072
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 217599 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...
Cannot determine thread, fp=0xbffa7638, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81f2143
0x84400a3
0x8440395
0x8407b1a
0x83c4289
0x83e9fb1
0x83ee2fb
0x83ee9d9
0x83ef5a2
0x833b07c
0x82b6ba0
0x82ab702
0x81f10ab
0x81f337a
0xb7c3d450
0x8164721
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read
http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
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.