2

I have this error in my syslog. I restored an older dump to solve this problem, after some reading. Now The errors in syslog are far less than before.

But still a few times an hour I get

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.

Anybody that knows how I can track what database is causing this issue? And how to fix?

2

1 Answer 1

2

There is inconsistency between the data files and the ib_logfile[0|1]-s. For me this can happen if I didn't run --apply-log when using innobackupex.

Try shut down the server, move the ib_logfiles into a different directory, and restart process. New logfiles will be created. (If it fails again, you can move back the original files)

2
  • I had this innodb is in the future message after resetting a broken slave using xtrabackup and could not work out why: I'd forgotten the --apply-log step - documentation now updated!
    – user76587
    Jun 10, 2016 at 10:15
  • Thanks so much for this. Only 2 hours of chasing my tail.
    – vr_driver
    Jan 13 at 1:11

Not the answer you're looking for? Browse other questions tagged or ask your own question.