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 &

查看导入进度:

pidstat -d 1可查看io运行的情况。

相关参考:

突发!某大厂机房掉电,MySQL数据库无法启动,紧急恢复过程...

Mysql异常停止之后的恢复操作

记一次断电导致的mysql数据恢复问题

相关推荐
写后端的胖头鱼1 小时前
【高频面试题】深分页问题
数据库·mysql·数据库优化·深分页
2601_962387825 小时前
多源数据查询指南:MySQL 联邦、Python 聚合与 Presto 引擎全对比
python·mysql·数据集成·presto·联邦查询
她说..5 小时前
MySQL JSON 处理学习文档
学习·mysql·json
写后端的胖头鱼6 小时前
【高频面试题】SQL 查询慢怎么排查
数据库·sql·mysql·oracle·慢查询·高频面试题
扬大平仔6 小时前
# 小深:用 AgentScope Java 2.0 Harness 做私人助手(上)mysql
java·开发语言·mysql
wudongfang6666 小时前
mysql全量同步数据改增量
数据库·mysql
garmin Chen7 小时前
MySQL精简面试题
数据库·后端·mysql·面试
服务端相声演员8 小时前
MySQL的select distinct ..Union all和select..union的区别
数据库·mysql
2501_930472448 小时前
深度复盘|数据库迁移实战(下):从自建 MySQL 5.7 到腾讯云 MySQL 8.0 的 SQL 兼容改造
数据库·mysql·腾讯云
leo_messi948 小时前
Mysql学习(十二) -- SQL执行到底做了什么事?
sql·学习·mysql