Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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?

share|improve this question

closed as off-topic by Jenny D, Andrew Schulman, masegaloeh, Hyppy, fuero Apr 28 at 13:59

  • This question does not appear to be about server, networking, or related infrastructure administration within the scope defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.

2  
Looks there's an answer there : dba.stackexchange.com/questions/8011/… –  bokan Sep 1 '12 at 12:50
4  
I'm voting to close this question as off-topic because it should have been migrated to Database Administrators but is now too old to migrate. –  Jenny D Apr 28 at 8:11

1 Answer 1

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)

share|improve this answer

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