root@host [/home/mysql2]# mysqld --user=mysql --datadir=/home/mysql2 --port=3307
071204 14:49:35 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...
071204 14:49:35 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 9089.
InnoDB: Doing recovery: scanned up to log sequence number 0 9089
071204 14:49:35 InnoDB: Error: page 7 log sequence number 3 1597302085
InnoDB: is in the future! Current system log sequence number 0 9089.
InnoDB: Your database may be corrupt.
071204 14:49:35 InnoDB: Error: page 1 log sequence number 3 3236834554
InnoDB: is in the future! Current system log sequence number 0 9089.
InnoDB: Your database may be corrupt.
071204 14:49:35 InnoDB: Error: page 3 log sequence number 3 1874267814
InnoDB: is in the future! Current system log sequence number 0 9089.
InnoDB: Your database may be corrupt.
071204 14:49:35 InnoDB: Error: page 4 log sequence number 3 3236863237
InnoDB: is in the future! Current system log sequence number 0 9089.
InnoDB: Your database may be corrupt.
071204 14:49:35 InnoDB: Error: page 11 log sequence number 3 1597303734
InnoDB: is in the future! Current system log sequence number 0 9089.
InnoDB: Your database may be corrupt.
071204 14:49:35 InnoDB: Error: page 6 log sequence number 3 3236147829
InnoDB: is in the future! Current system log sequence number 0 9089.
InnoDB: Your database may be corrupt.
071204 14:49:35 InnoDB: Error: page 475137 log sequence number 3 3236863123
InnoDB: is in the future! Current system log sequence number 0 9089.
InnoDB: Your database may be corrupt.
071204 14:49:35 InnoDB: Error: page 360461 log sequence number 3 3236862843
InnoDB: is in the future! Current system log sequence number 0 9089.
InnoDB: Your database may be corrupt.
071204 14:49:35 InnoDB: Error: page 360449 log sequence number 3 3236803056
InnoDB: is in the future! Current system log sequence number 0 9089.
InnoDB: Your database may be corrupt.
071204 14:49:35 InnoDB: Error: page 360464 log sequence number 3 3236147689
InnoDB: is in the future! Current system log sequence number 0 9089.
InnoDB: Your database may be corrupt.
071204 14:49:35 InnoDB: Error: page 344125 log sequence number 3 3235673660
InnoDB: is in the future! Current system log sequence number 0 9089.
InnoDB: Your database may be corrupt.
071204 14:49:35 InnoDB: Error: page 344065 log sequence number 3 3236829199
InnoDB: is in the future! Current system log sequence number 0 9089.
InnoDB: Your database may be corrupt.
071204 14:49:35 InnoDB: Error: page 458769 log sequence number 3 3135196313
InnoDB: is in the future! Current system log sequence number 0 9089.
InnoDB: Your database may be corrupt.
071204 14:49:35 InnoDB: Error: page 458753 log sequence number 3 3236863237
InnoDB: is in the future! Current system log sequence number 0 9089.
InnoDB: Your database may be corrupt.
071204 14:49:35 InnoDB: Error: page 327705 log sequence number 3 1987517532
InnoDB: is in the future! Current system log sequence number 0 9089.
InnoDB: Your database may be corrupt.
071204 14:49:35 InnoDB: Error: page 327681 log sequence number 3 3236764655
InnoDB: is in the future! Current system log sequence number 0 9089.
InnoDB: Your database may be corrupt.
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 1 row operations to undo
InnoDB: Trx id counter is 0 341255936
071204 14:49:35 InnoDB: Error: page 8 log sequence number 3 1597299707
InnoDB: is in the future! Current system log sequence number 0 9089.
InnoDB: Your database may be corrupt.
071204 14:49:35 InnoDB: Error: page 9 log sequence number 3 1597299778
InnoDB: is in the future! Current system log sequence number 0 9089.
InnoDB: Your database may be corrupt.
071204 14:49:35 InnoDB: Error: page 13 log sequence number 0 36808
InnoDB: is in the future! Current system log sequence number 0 9089.
InnoDB: Your database may be corrupt.
071204 14:49:35 InnoDB: Error: page 14 log sequence number 0 36808
InnoDB: is in the future! Current system log sequence number 0 9089.
InnoDB: Your database may be corrupt.
071204 14:49:35InnoDB: Starting rollback of uncommitted transactions
InnoDB: Error: page 15 log sequence number 0 36808
InnoDB: is in the future! Current system log sequence number 0 9089.
InnoDB: Your database may be corrupt.
InnoDB: Rolling back trx with id 0 341255424, 1 rows to undoInnoDB: Error: trying to access page number 2065550 in space 0,
InnoDB: space name ./ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10
071204 14:49:35InnoDB: Assertion failure in thread 3086960320 in file fil0fil.c line 3922
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=0xbfffbe1c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81346f0
0x82f1964
0x82bbea9
0x82bc1a8
0x82a89e3
0x82de11a
0x82de8e9
0x828784e
0x82a49ae
0x829a0c5
0x8295352
0x82242fc
0x82932db
0x82ce87a
0x8207188
0x81bc96c
0x81b3cdd
0x8137dc5
0x61ede3
0x80c77f1
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.