- 论坛徽章:
- 0
|
关键数据，因系统崩溃而丢失，而系统后来连mount都不行，后来请高手将数据寻找到节点dump出来了，但是将ibdata1文件恢复到安装好的系统上后，结果mysql连启动都无法启动，其中.err文件报错如下，
070604 23:42:18 mysqld started
070604 23:42:18 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...
070604 23:42:18 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 3039274508.
InnoDB: Doing recovery: scanned up to log sequence number 0 3039274508
070604 23:42:18 InnoDB: Error: page 7 log sequence number 2 704611911
InnoDB: is in the future! Current system log sequence number 0 3039274508.
InnoDB: Your database may be corrupt.
070604 23:42:18 InnoDB: Error: page 1 log sequence number 2 1061603780
InnoDB: is in the future! Current system log sequence number 0 3039274508.
InnoDB: Your database may be corrupt.
070604 23:42:18 InnoDB: Error: page 3 log sequence number 2 704612373
InnoDB: is in the future! Current system log sequence number 0 3039274508.
InnoDB: Your database may be corrupt.
070604 23:42:18 InnoDB: Error: page 2 log sequence number 2 1040143065
InnoDB: is in the future! Current system log sequence number 0 3039274508.
InnoDB: Your database may be corrupt.
070604 23:42:18 InnoDB: Error: page 4 log sequence number 2 1061606707
InnoDB: is in the future! Current system log sequence number 0 3039274508.
InnoDB: Your database may be corrupt.
070604 23:42:18 InnoDB: Error: page 11 log sequence number 2 704613686
InnoDB: is in the future! Current system log sequence number 0 3039274508.
InnoDB: Your database may be corrupt.
070604 23:42:18 InnoDB: Error: page 81921 log sequence number 2 1061603311
InnoDB: is in the future! Current system log sequence number 0 3039274508.
InnoDB: Your database may be corrupt.
070604 23:42:18 InnoDB: Error: page 51 log sequence number 2 1031437530
InnoDB: is in the future! Current system log sequence number 0 3039274508.
InnoDB: Your database may be corrupt.
InnoDB: Error: trying to access page number 1904367410 in space 0,
InnoDB: space name ./ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10
070604 23:42:18InnoDB: Assertion failure in thread 3076407424 in file fil0fil.c line 3853
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=20967424
max_used_connections=0
max_connections=500
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3700780 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=0xbfff909c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8126bf0
0x9c8f88
0x828e43e
0x828e43e
0x8280b61
0x827b9da
0x827c04f
0x8270c11
0x8270de2
0x8272efe
0x81f4c34
0x81ac21f
0x81a3806
0x8127f72
0x8128509
0x36f79a
0x80c40e1
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.
070604 23:42:18 mysqld ended
每次启动都是这样，我要疯了，我的数据呀，请高手指点一二！ |
|
免费注册
发表于 2007-06-04 23:52
发表于 2007-06-05 08:30
发表于 2007-06-05 13:02
