57,062
社区成员
发帖
与我相关
我的任务
分享mysql 数据库无法启动INNODB 怎么办求高手解决
131016 15:33:18 mysqld_safe Starting mysqld daemon with databases from /alidata/server/mysql/var
131016 15:33:18 InnoDB: Initializing buffer pool, size = 800.0M
131016 15:33:18 InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
131016 15:33: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...
131016 15:33:18 InnoDB: Error: page 7 log sequence number 110 2657205495
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 1 log sequence number 93 3574294358
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 3 log sequence number 93 3574294358
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 2 log sequence number 110 2705000881
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 4 log sequence number 110 2721370334
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 11 log sequence number 110 1269294416
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 62 log sequence number 4 1403116640
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 5 log sequence number 110 2791303633
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 6 log sequence number 110 2791553052
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 769 log sequence number 110 2892239346
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 77451818 in space 0,
InnoDB: space name /alidata/server/mysql/var/ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
131016 15:33:18 InnoDB: Assertion failure in thread 139702648760096 in file fil/fil0fil.c line 4135
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.1/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
07:33:18 UTC - mysqld got signal 6 ;
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=268435456
read_buffer_size=33554432
max_used_connections=0
max_threads=1024
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 67381600 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
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...
stack_bottom = 0 thread_stack 0x40000
/alidata/server/mysql/libexec/mysqld(my_print_stacktrace+0x29) [0x883349]
/alidata/server/mysql/libexec/mysqld(handle_fatal_signal+0x41a) [0x6db72a]
/lib64/libpthread.so.0(+0xf500) [0x7f0f0e7ed500]
/lib64/libc.so.6(gsignal+0x35) [0x7f0f0d6778a5]
/lib64/libc.so.6(abort+0x175) [0x7f0f0d679085]
/alidata/server/mysql/libexec/mysqld(fil_io+0x34e) [0x7a33fe]
/alidata/server/mysql/libexec/mysqld() [0x78be10]
/alidata/server/mysql/libexec/mysqld(buf_read_page+0x21d) [0x78c7ed]
/alidata/server/mysql/libexec/mysqld(buf_page_get_gen+0x363) [0x7863d3]
/alidata/server/mysql/libexec/mysqld(trx_undo_lists_init+0x41b) [0x8164cb]
/alidata/server/mysql/libexec/mysqld() [0x80ce81]
/alidata/server/mysql/libexec/mysqld(trx_rseg_list_and_array_init+0xa3) [0x80d0a3]
/alidata/server/mysql/libexec/mysqld(trx_sys_init_at_db_start+0x140) [0x80de20]
/alidata/server/mysql/libexec/mysqld(innobase_start_or_create_for_mysql+0xfef) [0x7ff0df]
/alidata/server/mysql/libexec/mysqld() [0x76ad6a]
/alidata/server/mysql/libexec/mysqld(ha_initialize_handlerton(st_plugin_int*)+0x31) [0x6cc8d1]
/alidata/server/mysql/libexec/mysqld() [0x753dfd]
/alidata/server/mysql/libexec/mysqld(plugin_init(int*, char**, int)+0x720) [0x755c50]
/alidata/server/mysql/libexec/mysqld() [0x5e5d4f]
/alidata/server/mysql/libexec/mysqld(main+0x1c6) [0x5e9df6]
/lib64/libc.so.6(__libc_start_main+0xfd) [0x7f0f0d663cdd]
/alidata/server/mysql/libexec/mysqld() [0x522479]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
131016 15:33:18 mysqld_safe mysqld from pid file /alidata/server/mysql/var/AY131011212338503c43Z.pid ended
这是错误日志 高手帮帮忙啊
131016 15:33:18 InnoDB: Initializing buffer pool, size = 800.0M
131016 15:33:18 InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
131016 15:33: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...
131016 15:33:18 InnoDB: Error: page 7 log sequence number 110 2657205495
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 1 log sequence number 93 3574294358
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 3 log sequence number 93 3574294358
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 2 log sequence number 110 2705000881
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 4 log sequence number 110 2721370334
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 11 log sequence number 110 1269294416
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 62 log sequence number 4 1403116640
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 5 log sequence number 110 2791303633
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 6 log sequence number 110 2791553052
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 769 log sequence number 110 2892239346
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 77451818 in space 0,
InnoDB: space name /alidata/server/mysql/var/ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
131016 15:33:18 InnoDB: Assertion failure in thread 139702648760096 in file fil/fil0fil.c line 4135
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.1/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
07:33:18 UTC - mysqld got signal 6 ;
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=268435456
read_buffer_size=33554432
max_used_connections=0
max_threads=1024
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 67381600 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
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...
stack_bottom = 0 thread_stack 0x40000
/alidata/server/mysql/libexec/mysqld(my_print_stacktrace+0x29) [0x883349]
/alidata/server/mysql/libexec/mysqld(handle_fatal_signal+0x41a) [0x6db72a]
/lib64/libpthread.so.0(+0xf500) [0x7f0f0e7ed500]
/lib64/libc.so.6(gsignal+0x35) [0x7f0f0d6778a5]
/lib64/libc.so.6(abort+0x175) [0x7f0f0d679085]
/alidata/server/mysql/libexec/mysqld(fil_io+0x34e) [0x7a33fe]
/alidata/server/mysql/libexec/mysqld() [0x78be10]
/alidata/server/mysql/libexec/mysqld(buf_read_page+0x21d) [0x78c7ed]
/alidata/server/mysql/libexec/mysqld(buf_page_get_gen+0x363) [0x7863d3]
/alidata/server/mysql/libexec/mysqld(trx_undo_lists_init+0x41b) [0x8164cb]
/alidata/server/mysql/libexec/mysqld() [0x80ce81]
/alidata/server/mysql/libexec/mysqld(trx_rseg_list_and_array_init+0xa3) [0x80d0a3]
/alidata/server/mysql/libexec/mysqld(trx_sys_init_at_db_start+0x140) [0x80de20]
/alidata/server/mysql/libexec/mysqld(innobase_start_or_create_for_mysql+0xfef) [0x7ff0df]
/alidata/server/mysql/libexec/mysqld() [0x76ad6a]
/alidata/server/mysql/libexec/mysqld(ha_initialize_handlerton(st_plugin_int*)+0x31) [0x6cc8d1]
/alidata/server/mysql/libexec/mysqld() [0x753dfd]
/alidata/server/mysql/libexec/mysqld(plugin_init(int*, char**, int)+0x720) [0x755c50]
/alidata/server/mysql/libexec/mysqld() [0x5e5d4f]
/alidata/server/mysql/libexec/mysqld(main+0x1c6) [0x5e9df6]
/lib64/libc.so.6(__libc_start_main+0xfd) [0x7f0f0d663cdd]
/alidata/server/mysql/libexec/mysqld() [0x522479]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
131016 15:33:18 mysqld_safe mysqld from pid file /alidata/server/mysql/var/AY131011212338503c43Z.pid ended
这是错误日志 高手帮帮忙啊
...全文
请发表友善的回复…
发表回复
kobe8free 2013-10-16
- 打赏
- 举报
那就只有按照九楼说的来了，能找到以前的备份也好！
下次记得要做数据备份哦！物理分区的备份
ACMAIN_CHM 2013-10-16
- 打赏
- 举报
文件损坏，按楼上的方法试一下吧。如果不行就只能找以前的备份了。
liuxinran819 2013-10-16
- 打赏
- 举报
可能是InnoDB数据文件损坏了 先不要继续操作了 先把数据和配置文件备份一下防止乱弄把数据全弄坏了 然后再用副本试着恢复
关于InnoDB的数据恢复 错误日志提示参照下面的网址：
http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
你可以试着设定不同的innodb_force_recovery系统变量来重新启动MySQL 看看是不是有可以启动起来的值
祝你好运！
ikenbor 2013-10-16
- 打赏
- 举报
8个G的数据 非常重要 
kobe8free 2013-10-16
- 打赏
- 举报
现在的状况是不能打开数据表，得不到数据吧！
你的数据是不是很重要
如果觉得数据无所谓，而是只要可以正常的使用数据库
建议你把ibdata和日志文件都删掉。重启就可以正常运转了！
ikenbor 2013-10-16
- 打赏
- 举报
数据库突然中止 之后重启就这样了 在之前操作了一次表索引
ikenbor 2013-10-16
- 打赏
- 举报
我并没有进行拷贝
ikenbor 2013-10-16
- 打赏
- 举报
ib_logfile0和ib_logfile1 更改了名字 重新生成了日志文件仍然提示这种报错
rucypli 2013-10-16
- 打赏
- 举报
把ib_logfile0和ib_logfile1重命名 然后重启试试
iihero 2013-10-16
- 打赏
- 举报
应该是log file和ibdata不匹配造成的。
kobe8free 2013-10-16
- 打赏
- 举报
innoDB是可以启动的，说日志序列号和ibdata文件中的不匹配！
你是不是copy ibdata到新的mysql的时候没有copy ib_logfile0和ib_logfile1
