利用 Forcing InnoDB Recovery 特性解决 MySQL 重启失败的问题

奉君逍遥

已于 2024-06-27 10:59:56 修改

阅读量1.6k

点赞数

分类专栏： Linux 文章标签： mysql 数据库

于 2023-09-27 15:49:06 首次发布

本文链接：https://blog.youkuaiyun.com/hwx865/article/details/133351745

版权

当MySQL因异常断电或系统重启无法启动时，可通过设置innodb_force_recovery来强制恢复。本文详细介绍了分析问题、设置恢复模式、备份恢复数据的步骤，并提醒在使用此方法时应注意数据安全，最好先备份。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

问题

由于异常断电或者系统异常重启时 MySQL 没有正常退出导致 MySQL 无法启动，启动时报错如下：

[System] [Server] /usr/sbin/mysqld (mysqld 8.0.30) starting as process 2665
[System] [InnoDB] InnoDB initialization has started.
[System] [InnoDB] InnoDB initialization has ended.
[ERROR] [InnoDB] Assertion failure: fut0lst.ic:81:addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA thread 140254438749952
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/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
08:02:18 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x7f8f