mysql重启后报错
重启mysql服务后
查看innodb参数 发现都不见了
查看引擎 发现没有innodb引擎没有了
查看Error log 如下：
InnoDB: bounds; space id 0 page number 89977, page 121 in doublewrite buf.
InnoDB: Warning: a page in the doublewrite buffer is not within space
InnoDB: bounds; space id 0 page number 89978, page 122 in doublewrite buf.
InnoDB: Warning: a page in the doublewrite buffer is not within space
InnoDB: bounds; space id 0 page number 89979, page 123 in doublewrite buf.
InnoDB: Warning: a page in the doublewrite buffer is not within space
InnoDB: bounds; space id 0 page number 89980, page 124 in doublewrite buf.
InnoDB: Warning: a page in the doublewrite buffer is not within space
InnoDB: bounds; space id 0 page number 89981, page 125 in doublewrite buf.
InnoDB: Warning: a page in the doublewrite buffer is not within space
InnoDB: bounds; space id 0 page number 89982, page 126 in doublewrite buf.
InnoDB: Warning: a page in the doublewrite buffer is not within space
InnoDB: bounds; space id 0 page number 89983, page 127 in doublewrite buf.
InnoDB: Error: trying to access page number 13199 in space 0,
InnoDB: space name ./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.
120920 16:41:25 InnoDB: Assertion failure in thread 3086124752 in file fil/fil0fil.c line 4123
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-recovery.html
InnoDB: about forcing recovery.
120920 16:41:25 – 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=8384512
read_buffer_size=131072
max_used_connections=0
max_threads=151
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337730 K
bytes of memory
Hope that’s ok; if not, decrease some variables in the equation.
thd: 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 = (nil) thread_stack 0x30000
/usr/local/mysql/libexec/mysqld(my_print_stacktrace+0x22) [0x839cf62]
/usr/local/mysql/libexec/mysqld(handle_segfault+0x37f) [0x81bb54f]
[0xb7f35400]
/lib/libc.so.6(abort+0x101) [0x4c5e2451]
/usr/local/mysql/lib/mysql/plugin/ha_innodb.so(fil_io+0x39c) [0xb6e6881c]
/usr/local/mysql/lib/mysql/plugin/ha_innodb.so [0xb6e4cca4]
/usr/local/mysql/lib/mysql/plugin/ha_innodb.so(buf_read_page+0x273) [0xb6e4d223]
/usr/local/mysql/lib/mysql/plugin/ha_innodb.so(buf_page_get_gen+0x114) [0xb6e45994]
/usr/local/mysql/lib/mysql/plugin/ha_innodb.so(trx_undo_lists_init+0x1b9) [0xb6eebd59]
/usr/local/mysql/lib/mysql/plugin/ha_innodb.so [0xb6ee2db4]
/usr/local/mysql/lib/mysql/plugin/ha_innodb.so(trx_rseg_list_and_array_init+0xa1) [0xb6ee2fe1]
/usr/local/mysql/lib/mysql/plugin/ha_innodb.so(trx_sys_init_at_db_start+0x171) [0xb6ee3e51]
/usr/local/mysql/
