Description:
After reboot mysqld doesn't start.
In mysqld.err I see:
080206 18:38:30 InnoDB: Error: page 7 log sequence number 4 1835226804
InnoDB: is in the future! Current system log sequence number 0 8716.
InnoDB: Your database may be corrupt.
080206 18:38:30 InnoDB: Error: page 1 log sequence number 4 1744001616
InnoDB: is in the future! Current system log sequence number 0 8716.
InnoDB: Your database may be corrupt.
080206 18:38:30 InnoDB: Error: page 3 log sequence number 3 1437693694
InnoDB: is in the future! Current system log sequence number 0 8716.
InnoDB: Your database may be corrupt.
080206 18:38:30 InnoDB: Error: page 2 log sequence number 4 1744826954
InnoDB: is in the future! Current system log sequence number 0 8716.
InnoDB: Your database may be corrupt.
080206 18:38:30 InnoDB: Error: page 4 log sequence number 4 3265500636
InnoDB: is in the future! Current system log sequence number 0 8716.
InnoDB: Your database may be corrupt.
080206 18:38:30 InnoDB: Error: page 11 log sequence number 3 1046816183
InnoDB: is in the future! Current system log sequence number 0 8716.
InnoDB: Your database may be corrupt.
080206 18:38:30 InnoDB: Error: page 180246 log sequence number 3 1046816183
InnoDB: is in the future! Current system log sequence number 0 8716.
InnoDB: Your database may be corrupt.
080206 18:38:30 InnoDB: Error: page 180225 log sequence number 3 2228312222
InnoDB: is in the future! Current system log sequence number 0 8716.
InnoDB: Your database may be corrupt.
080206 18:38:30 InnoDB: Error: page 5 log sequence number 0 8726
InnoDB: is in the future! Current system log sequence number 0 8716.
InnoDB: Your database may be corrupt.
080206 18:38:30 InnoDB: Error: page 6 log sequence number 4 836470622
InnoDB: is in the future! Current system log sequence number 0 8716.
InnoDB: Your database may be corrupt.
080206 18:38:30 InnoDB: Error: page 45 log sequence number 4 3273875023
InnoDB: is in the future! Current system log sequence number 0 8716.
InnoDB: Your database may be corrupt.
InnoDB: Error: trying to access page number 979 in space 0
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10
080206 18:38:30 InnoDB: Assertion failure in thread 16384 in file fil0fil.c line 1204
InnoDB: Failing assertion: 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to mysql@lists.mysql.com
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=134217728
read_buffer_size=1044480
max_used_connections=0
max_connections=10
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 151511 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x840c548
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 (ebp) is NULL, did you compile with
-fomit-frame-pointer? Aborting backtrace!
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0xeeedeceb is invalid pointer
thd->thread_id=489
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.
How I can fix it?
How to repeat:
I dont now.
