mysql:记一次8.0的force recovery

已于 2023-06-18 23:29:13 修改
阅读量1.6k 收藏 1
点赞数 3
文章标签： 数据库 运维 force recovery mysql
于 2023-06-18 17:11:25 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/q195136130/article/details/131272971
版权
记录了在Ubuntu系统中MySQL8.0.33遭遇存储故障后的数据库恢复过程，包括查找入口点、错误日志分析、参数配置以及解决InnoDB表空间页的未来日志序列号错误，最终通过处理异常的binlog.index文件使数据库成功启动。

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

环境是ubuntu上安装的mysql 8.0.33。

存储掉链路导致大面积虚拟机故障。现在虚拟机恢复后，强起数据库。

找入口

客户的环境都是两眼一抹黑，得先找下入口：error日志、启停方式、参数文件、datadir

mysql的环境千奇百怪。以下我举几个比较典型的情况

error日志：datadir下，/var/log/下，/var/log/mysql下

启停方式：mysqld命令调，mysqld_safe命令调，service命令调，systemctl命令调

参数文件：不同于redhat平台，ubuntu下的不在/etc/my.cnf，最终找到
在/etc/mysql/mysql.conf.d/mysqld.cnf

datadir:以参数文件里为准，默认是/var/lib/mysql

这次的入口是

error日志：/var/log/mysql

启停方式：mysqld

参数文件：/etc/mysql/mysql.conf.d/mysqld.cnf

datadir：/var/lib/mysql

参数调试

现无参数启动，查看日志

2023-06-18T06:48:17.310158Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.33-0ubuntu0.22.04.2) starting as process 243435
2023-06-18T06:48:17.329488Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2023-06-18T06:48:17.664807Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=132] log sequence number 16436137916 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.665003Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.665078Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=131] log sequence number 20993540698 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.665175Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=130] log sequence number 20998638164 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.665325Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.665267Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.665395Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=129] log sequence number 16443358485 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.665447Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=231] log sequence number 21000237271 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.665570Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.665195Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=280] log sequence number 21000766607 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.665683Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.665736Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=1029] log sequence number 20998638164 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.665794Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.665571Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.665569Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=199] log sequence number 20993540698 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.665937Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=128] log sequence number 20993540655 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.665952Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.665980Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.665974Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=184] log sequence number 21000400583 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.666064Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=269] log sequence number 21000213113 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.666094Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.665969Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=138] log sequence number 21000184075 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.666136Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.666318Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=427] log sequence number 16443358485 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.666259Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.666196Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=270] log sequence number 21000259205 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.666384Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.666404Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=355] log sequence number 20993540655 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.666655Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.666539Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=127] log sequence number 20998638121 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.666748Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=126] log sequence number 20995496226 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.666819Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.666861Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=125] log sequence number 20991826172 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.666523Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.666918Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.666829Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.667035Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=431] log sequence number 21000194944 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.667118Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.667061Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=124] log sequence number 20997845839 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.667079Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=166] log sequence number 20995496226 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.667244Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.667282Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.667232Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=376] log sequence number 20991826172 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.667358Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=198] log sequence number 20997845839 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.666972Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=210] log sequence number 20998638121 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.667442Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.667380Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.667489Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.667382Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=230] log sequence number 20998628295 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.667562Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=123] log sequence number 16437096125 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.667610Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.667650Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.667582Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=122] log sequence number 16438379070 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.667633Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=295] log sequence number 21000204145 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.667781Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=424] log sequence number 16437096125 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.667809Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=121] log sequence number 20998638067 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.667791Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.667874Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.667723Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.667875Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.668007Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=120] log sequence number 21001668244 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.668036Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=220] log sequence number 21000237933 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.668081Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.668063Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=229] log sequence number 21001674898 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.668065Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=354] log sequence number 16450098654 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.668119Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.668192Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.668196Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=407] log sequence number 21000142454 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.668385Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=292] log sequence number 20998638067 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.668251Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.668423Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.668341Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=143] log sequence number 21000385255 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.668502Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.668518Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=119] log sequence number 16450079420 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.668424Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.668593Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=1061] log sequence number 21001668244 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.668554Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.668680Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.668709Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=117] log sequence number 21000237971 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.668804Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=116] log sequence number 20998638029 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.668602Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=118] log sequence number 20991826096 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.668944Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.668866Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=395] log sequence number 21000168326 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.668860Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.668861Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.669138Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=363] log sequence number 21001651641 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.669040Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=180] log sequence number 21001664034 is in the future! Current system log sequence number 2733965836.
2023-06-18T06:48:17.669183Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.669047Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.669218Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-06-18T06:48:17.669262Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=320] log sequence number 21000237971 is in the future! Current sys
最低0.47元/天 解锁文章
foxytale
关注
mysql recovery_MySQL Recovery
weixin_33514221的博客
01-18 2158
MySQL Recovery最新版是一款实用的MySQL数据库恢复工具。MySQLRecovery官方版复的数据库有多种导出模式，包括通过服务器连接，使用ODBC驱动程序。包含创建表的命令、键字段和在表中插入行的命令的sql文件。MySQLRecovery最新版可以从任何复杂的文件中执行MySQL数据库恢复。MySQL Recovery基本简介MySQL Recovery是十分实用的MySQL数据...
recovery for mysql_Recovery Toolbox for MySQL（MySQL数据库修复软件） V 2.0.3.0 官方版
weixin_34609222的博客
01-30 935
Recovery Toolbox for MySQL是款高效稳定的MySQL数据库修复工具，辅助用户迅速从损坏的MySQL数据库中恢复数据，支持大多数数据库格式，完成后，可以保存为SQL脚本，也可以导入到MySQL服务器数据库。Recovery Toolbox for MySQL功能1、恢复损坏的MyISAM数据库格式2、恢复损坏的InnoDB数据库格式3、将恢复的数据保存为SQL脚本4、将恢复的...
使用innodb_force_recovery解决MySQL崩溃无法重启问题
12-15
一 背景 某一创业的朋友的主机因为磁盘阵列损坏机器crash,重启MySQL服务时 报如下错误: 代码如下: InnoDB: Reading tablespace information from the .ibd files… InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer… InnoDB: Doing recovery: scanned up to log sequence number 9120034833 150125 16:12:51 InnoDB: Sta
【案例】利用innodb_force_recovery 解决MySQL服务器crash无法重启问题
cojm55771的博客
02-25 393
一 背景 某一创业的朋友的主机因为磁盘阵列损坏机器crash,重启MySQL服务时 报如下错误: InnoDB: Reading tablespace information from the ...
mysql force recovery,用innodb_force_recovery 修复崩溃的MySQL数据库
weixin_34113453的博客
03-17 569
今天一大早访问网站，发现打不开了，提示数据库连接错误。重启服务器不起作用，一直提示ERROR! MySQL server PID file could not be found!查看/usr/local/mysql/var 目录下 CentOS错误日志 VM_14_80_centos.err，发现从昨晚23:04分开始，MySQL就已经报错，错误出在InnoDB引擎上。170104 23:04:...
从MySQL5.7平滑升级到MySQL8.0的最佳实践分享
最新发布
m0_74824517的博客
03-02 685
升级需求：将5.7.35升级到8.0.27, 升级方式 in-place升级【关闭现有版本MySQL，将二进制或包替换成新版本并在现有数据目录上启动MySQL并执行升级任务的方式，称为in-place升级】以下Mysql 生命周期-内容来自于互联网关于数据库版本升级，一直都是热议话题，对于升级的缘由各家也有所不同，有业务驱动的，有DBA自发驱动的，有规划导向也有方向指引的……抛开各种原因，当升级这个决定落下来的时候，对于DBA手头的几百几千套数据库来说，就好比是一场动物大迁徙，满满的画面感。从Oracle发
MySQL8.0——数据库克隆
qtishero的博客
10-18 1033
MySQL8.0.17引入clone plugin，允许从本地或者远程的MySQL中克克隆的数据是InnoDB存储引擎中的物理快照信息（包括schema,表，表空间，元数据等克隆的数据是一个完整的数据目录，插件可以使用克隆的目录恢复和恢复一个mysql server。克隆的数据是InnoDB存储引擎中的物理快照信息。
docker 下运行容器加 mysql5.7.37 或docker 下运行容器加 mysql8.0本地mysql 数据库服务搭建
weixin_43186648的博客
02-21 1348
docker 下跑 localhost 的 mysql 服务docker localhost mysql 服务容器时区问题mysql5737或mysql5.7.37mysql8.0或mysql80创建数据库 docker localhost mysql 服务 容器时区问题 mysql5737或mysql5.7.37 mysql8.0或mysql80 1000 docker run -p 3308:3306 --name comysql_v8.0 -e MYSQL_ROOT_PASSWORD=123456
MySQL 8.0 安装脚本
虫虫的博客
02-01 903
MySQL 8.0 安装脚本
mysql force recovery_使用innodb_force_recovery解决MySQL崩溃无法重启问题
weixin_30014783的博客
02-03 955
一 背景某一创业的朋友的主机因为磁盘阵列损坏机器crash,重启MySQL服务时 报如下错误:复制代码 代码如下:InnoDB: Reading tablespace information from the .ibd files...InnoDB: Restoring possible half-written data pages from the doublewriteInnoDB: buf...
mysql-recovery:恢复大数据库文件 (.sql)
07-06
mysql-recovery 恢复大数据库文件 (.sql) rycovery 数据库没有得到 max_execution_time 错误
mysql --force -f_MySQL--使用innodb_force_recovery修复数据库异常
weixin_28731223的博客
01-27 507
当MySQL服务异常重启失败后，可以通过配置参数innodb_force_recovery来对MySQL服务进行修复启动。参数innodb_force_recovery选项：1 (SRV_FORCE_IGNORE_CORRUPT): 忽略检查到的 corrupt 页。尽管检测到了损坏的 page 仍强制服务运行。一般设置为该值即可，然后 dump 出库表进行重建。2 (SRV_FORCE_NO_B...
mysql 强制innoDB恢复
qq_31315703的博客
04-28 1734
https://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html [mysqld] innodb_force_recovery = 1 默认情况下，innodb_force_recovery为 0（正常启动而不强制恢复）。innodb_force_recovery允许的非零值为 1 到 6。较大的值包括较小值的功能。例如，值 3 包括值 1 和 2 的所有功能。 如果您能够转储innodb_force_recovery值为 3 或更小
一次mysql无缘无故的挂掉，使用innodb_force_recovery修复
weixin_33937913的博客
05-23 2929
最近遇到了一个比较奇怪的问题，在大家都在睡午觉的时候，突然手机响了起来，我为了不吵醒其他人拿起了手机看了看监控信息，我去，居然是数据库down了，这是一台运行很久的数据库服务器，当我登进去服务器的时候，尝试重启mysql，但是报（Starting MySQL..... ERROR! The server quit without updating PID file (...
详解MySQL修复innodb：innodb_force_recovery
牛肉胡辣汤
11-29 1283
是MySQL中的一个参数，可以设置为不同的整数值。它用于启动InnoDB存储引擎的"紧急恢复模式"，当InnoDB遇到严重的问题时，通过设置不同的值来尝试修复数据。的取值范围是0到6，取值越大，尝试修复的方式越严格。但是需要注意的是，设置一个过高的值可能会导致数据丢失。
mysql 强制InnoDB恢复 innodb_force_recovery详解
热门推荐
yangydq的专栏
10-26 1万+
mysql5.7 强制innoDB恢复 innodb_force_recovery mysql无法启动 数据库恢复
MySQL的innodb_force_recovery
MyFreeIT
10-27 6710
MySQL在转储文件或者导入数据的过程中，出现中断、失败或者异常，造成数据无法回滚，可以通过innodb_force_recovery强力迫使InnoDB存储引擎运行，同时阻止后台操作运行，以便转储表。 [mysqld] innodb_force_recovery = 1 innodb_force_recovery的有6个可选项，如下所示，更详细的描述请查阅官方文档。 innodb_force_recovery 描述 1 SRV_FORCE_IGNORE_CORRUPT 2 SRV_F
mysql update 会自动加锁吗_MySQL 意外宕机不难解决，数据会丢么？但你真的懂数据恢复吗？...
weixin_40006963的博客
12-01 154
点击上面蓝色字体关注我们技术 / 架构 / 职场 / 面试关注即送：4000G 架构师视频来源：sq.163yun.com/blog/article/172546631668785152InnoDB如果发生意外宕机了，数据会丢么？对于这个问题，稍微了解一点MySQL知识的人，都会斩钉截铁的回答：不会！为什么？他们也会毫不犹豫地说：因为有重做日志(redo log)，数据可以通过r...
mysql8.0.40服务无法启动
12-30
此时可借助 innodb_force_recovery 参数逐步增加其值(从1到6) 来强制打开受损的日志文件进而实施相应的挽救策略. #### 更新操作系统补丁包以及驱动程序 保持主机系统的最新状态有助于排除因外部依赖关系引发的服务...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值