欢迎您访问程序员文章站本站旨在为大家提供分享程序员计算机编程知识!
您现在的位置是: 首页  >  数据库

非正常关机时,innodb故障导致mysql无法启动的解决方法_MySQL

程序员文章站 2024-02-10 18:10:04
...
bitsCN.com
非正常关机时,innodb故障导致mysql无法启动的解决方法 一次非正常关机,mysql无法启动。查看err日志,显示: InnoDB: Starting crash recovery.InnoDB: Reading tablespace information from the .ibd files...InnoDB: Restoring possible half-written data pages from the doublewriteInnoDB: buffer...InnoDB: Error: trying to access page number 4294899072 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 thatInnoDB: your my.cnf matches the ibdata files that you have in theInnoDB: MySQL server. 120331 1:03:41 InnoDB: Assertion failure in thread 3078932288 in file fil0fil.c line 4409InnoDB: 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, evenInnoDB: immediately after the mysqld startup, there may beInnoDB: corruption in the InnoDB tablespace. Please refer toInnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.htmlInnoDB: about forcing recovery. 21:03:41 UTC - mysqld got signal 6 ; 没办法,只好在/etc/my.cnf中写入[mysqld] innodb_force_recovery = 4 但是仍然无法启动。改为:innodb_force_recovery = 6数据库可以读出来,在6的情况下,是无法修改数据库的,也无法插入,只能导出。 用mysqldump导出,再把innodb_force_recovery改为0,但是数据无法导入。 最后还是删除了数据库重建。 这是第二次遇到这种错误,标记一下。
作者 lsstarboy bitsCN.com
相关标签: mysql 正常