记一次服务器宕机后数据库恢复的过程

hoxis

于 2017-09-20 14:12:49 发布

阅读量7.5k

点赞数 2

分类专栏：杂七杂八文章标签：数据库 mysql

本文链接：https://blog.youkuaiyun.com/bruce_6/article/details/78040231

版权

本文记录了一次数据库服务器宕机后的恢复过程，包括设置InnoDB恢复模式、恢复模式下启动MySQL、数据备份、原数据清理、数据恢复等步骤。在恢复过程中，通过调整my.cnf配置，逐级尝试恢复模式，最终成功启动数据库并进行数据恢复。

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

现象

现象很简单，数据库服务器被宕机，当然是在没有停数据库服务的情况下。

机器重启后，试图重启MySQL服务，无果，查看错误日志：

170920  0:30:17  InnoDB: Assertion failure in thread 140107687212800 in file /export/home/pb2/build/sb_0-2629600-1291399482.5/mysql-5.5.10/storage/innobase/include/fut0lst.ic line 83
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
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.
170920  0:30:17 - 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

最低0.47元/天解锁文章