☰

Mysql - innoDb - 未来可期！当前系统日志序列号

tag-icon • tag-icon mysql mysql5
Mysql - innoDb - 未来可期！当前系统日志序列号

我的系统日志中出现了这个错误。经过一番阅读后，我恢复了一个较旧的转储来解决这个问题。现在系统日志中的错误比以前少了很多。

但每小时我还是会遇到几次

Sep  1 14:23:29 homer mysqld: 120901 14:23:29  InnoDB: Error: page 96637 log sequence number 7 1223357717
Sep  1 14:23:29 homer mysqld: InnoDB: is in the future! Current system log sequence number 6 647303887.
Sep  1 14:23:29 homer mysqld: InnoDB: Your database may be corrupt or you may have copied the InnoDB
Sep  1 14:23:29 homer mysqld: InnoDB: tablespace but not the InnoDB log files. See
Sep  1 14:23:29 homer mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
Sep  1 14:23:29 homer mysqld: InnoDB: for more information.
Sep  1 14:23:29 homer mysqld: 120901 14:23:29  InnoDB: Error: page 96638 log sequence number 8 150027924
Sep  1 14:23:29 homer mysqld: InnoDB: is in the future! Current system log sequence number 6 647303887.
Sep  1 14:23:29 homer mysqld: InnoDB: Your database may be corrupt or you may have copied the InnoDB
Sep  1 14:23:29 homer mysqld: InnoDB: tablespace but not the InnoDB log files. See
Sep  1 14:23:29 homer mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
Sep  1 14:23:29 homer mysqld: InnoDB: for more information.
Sep  1 14:23:29 homer mysqld: 120901 14:23:29  InnoDB: Error: page 96639 log sequence number 7 4208567151
Sep  1 14:23:29 homer mysqld: InnoDB: is in the future! Current system log sequence number 6 647303887.
Sep  1 14:23:29 homer mysqld: InnoDB: Your database may be corrupt or you may have copied the InnoDB
Sep  1 14:23:29 homer mysqld: InnoDB: tablespace but not the InnoDB log files. See
Sep  1 14:23:29 homer mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
Sep  1 14:23:29 homer mysqld: InnoDB: for more information.

有人知道我该如何追踪导致此问题的数据库吗？以及如何修复？

答案1

数据文件和 ib_logfile[0|1]-s 之间存在不一致。如果我在使用 innobackupex 时没有运行 --apply-log，就会发生这种情况。

尝试关闭服务器，将 ib_logfiles 移至其他目录，然后重新启动进程。将创建新的日志文件。（如果再次失败，您可以移回原始文件）

相关内容