081107 22:53:01 mysqld started
081107 22:53:01 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...
081107 22:53:01 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 3 1961684663.
InnoDB: Error: tried to read 65536 bytes at offset 0 4544000.
InnoDB: Was only able to read 10752.
InnoDB: Fatal error: cannot read from file. OS error number 17.
081107 22:53:26InnoDB: Assertion failure in thread 4096 in file os0file.c line 2
107
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/mysql/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=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=0xbff2ba48, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x808b193
0x82deab8
0x8276810
0x8277f4f
0x822f803
0x8207be9
0x820eec1
0x820f6b9
0x813eee9
0x80fd9e4
0x80f641b
0x808c3b8
0x808c772
0x82e6ba4
0x8048101
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.
081107 22:53:26 mysqld ended
