InnoDB: corruption in the InnoDB tablespace

磁盘空间满和断电都可能导致mysql无法启动,报错如下:

复制代码
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.
20241031 10:54:24 [ERROR] 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.
To report this bug, see http://kb.askmonty.org/en/reporting-bugs
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.

处理步骤:

添加innodb_force_recovery参数的my.cnf强制启动-->导出全部数据库-->去掉innodb_force_recovery参数的my.cnf-->删除mysql数据目录重新初始化-->导入数据sql。

处理过程:

docker ps检查运行的容器

1.此次my.cnf设置innodb_force_recovery = 3后成功启动(正常从1-6按顺序尝试)

2.导出全部数据库:建议写成脚本后台跑

复制代码
docker exec mysql-master-dev mysqldump  -h127.0.0.1 -uroot -pxxx  --log-error=/var/lib/mysql/db_bak_dby_log.err --ssl-mode=DISABLED  --all-databases >./all.sql

3.关闭容器:

docker-compose -f docker-compose.yml down

4.进入data数据目录,删除所有文件rm -rf *,然后启动容器,自动重新初始化:

docker-compose -f docker-compose.yml up -d

5.进入容器检查mysql:

docker exec -it mysql-master-dev /bin/bash

root@14f086133dda:/# mysql -h127.0.0.1 -uroot -pxxx

mysql: [Warning] Using a password on the command line interface can be insecure.

Welcome to the MySQL monitor. Commands end with ; or \g.

Your MySQL connection id is 13

Server version: 8.0.26 MySQL Community Server - GPL

Copyright (c) 2000, 2021, Oracle and/or its affiliates.

Oracle is a registered trademark of Oracle Corporation and/or its

affiliates. Other names may be trademarks of their respective

owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> show databases;

+--------------------+

| Database |

+--------------------+

| |没有新库。

如果导出的脚本没有创建库命令,则先把库建上。create database db;

6.导入数据:使用脚本后台方式,避免网络超时断开。

root@localhost bak\]# cat db.sh docker exec -i mysql-master-dev mysql -h127.0.0.1 -uroot -pxxx \< all.sql \[root@localhost bak\]# chmod +x db.sh \[root@localhost bak\]# nohup ./db.sh \> ./dby.log \& 查看导入进度: ![](https://i-blog.csdnimg.cn/direct/ee7f8e35d372440db43ec8e3d7a99f7f.png) pidstat -d 1可查看io运行的情况。 ![](https://i-blog.csdnimg.cn/direct/df1dabbe045f4a5499be5437e378a55f.png) 相关参考: [突发!某大厂机房掉电,MySQL数据库无法启动,紧急恢复过程...](https://mp.weixin.qq.com/s/JRbAan2xktb1MKE-SVx_ig "突发!某大厂机房掉电,MySQL数据库无法启动,紧急恢复过程...") [Mysql异常停止之后的恢复操作](https://mp.weixin.qq.com/s/16UgVtYoWrU4G24JmSGBbA "Mysql异常停止之后的恢复操作") [记一次断电导致的mysql数据恢复问题](https://mp.weixin.qq.com/s/0MOIn-F9ZKP0tEsJVn77Pw "记一次断电导致的mysql数据恢复问题")

相关推荐
ZHOU_World1 小时前
数据库主从同步
数据库·mysql
茉莉玫瑰花茶1 小时前
MySQL 用户管理
数据库·mysql
博一波1 小时前
MySQL 备份与复制:类似“手机数据管理”
数据库·mysql
专注代码七年3 小时前
查询 mysql中 所有的 非空记录字段
数据库·mysql
程序新视界3 小时前
仅仅会用MySQL的EXPLAIN还不够,还需要会用EXPLAIN ANALYZE
mysql
jc06204 小时前
4.2-中间件之MySQL
数据库·mysql
伤心男孩拯救世界(Code King)4 小时前
【MySQL】--- 表的约束
数据库·mysql
不想被吃掉氩4 小时前
MySQL的性能优化。
数据库·mysql·性能优化
DemonAvenger5 小时前
数据库日志系统深度解析:从binlog到redo/undo日志的实践指南
数据库·mysql·性能优化
潘潘潘潘潘潘潘潘潘潘潘潘5 小时前
【MySQL】从零开始学习MySQL:基础与安装指南
linux·运维·服务器·数据库·学习·mysql