Any better way out of MySQL InnoDB log "in the future"? I've got this InnoDB error in MySQL 5.0.  Mysqld was stopped cleanly, but I managed to lose ib_logfile0 &amp; ib_logfile1 afterward.  Now after a clean startup, InnoDB has done its "crash recovery".  I went through the innodb_force_recovery=4 business, repaired a hung MyISAM table, and now replication is ready to go, apart from this.  Big numbers commified:

111116 15:49:36  InnoDB: Error: page 393457 log sequence number 111 561,760,232
InnoDB: is in the future! Current system log sequence number 70 3,946,969,851.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.


This is on a slave server.  The above error spews by the hundreds.  I found this answer: "insert and delete > 64 GB worth of data, so that the log sequence number becomes inflated big enough".  

http://forums.mysql.com/read.php?22,50163,50163#msg-50163


That magic number of 64GB comes from 4GB*16 where that guy's innodb log "major number" needed to increase from 0 to 15.  Mine's going from 70 to 111 = 164 GB.  This will take 5 days.  I'll keep working on speeding up my script, and running it in parallel to speed this up.  In the meantime, I'm hoping someone else has a better answer.  This is silly.
This was a pretty rare situation.  I hope to never end up there again, with an InnoDB "log sequence number is in the future!" error.  Because of my particular details, rebuilding/restoring my server's data was a last resort.  Some cheats in helping that were good ideas, but in the end, I decided to just keep improving my Perl script to play this silly game and churn through as many gigs/hour as I could.  What the heck, it's a good system stress test.

Remember: the goal is to increase a single counter ("log sequence number") which is stored somewhere in the headers of ib_logfile0 and ib_logfile1.  This is to fake out InnoDB so it will ignore an apparent time warp and get on with life.  But no one knows how to edit that number. Or if they do know, no one's talking. 

Here's my final product.  YMMV, but using mysql's REPEAT function to generate the data internally is highly efficient. 

 #!/usr/bin/perl
 use DBI;
 $table = shift || die;
 $dbh = DBI-&gt;connect("DBI:mysql:junk:host=localhost", "user", "pass"); #Edit "junk" (DB name), user, and pass to suit.
 $dbh-&gt;do("DROP TABLE IF EXISTS $table");
 $dbh-&gt;do("CREATE TABLE $table (str TEXT) ENGINE=INNODB");
 $sth = $dbh-&gt;prepare("INSERT INTO $table (str) VALUES (REPEAT(?,1000000))");
 foreach (1..50) {
    $sth-&gt;execute('0123456789');   # 10 MB
 }
 $dbh-&gt;do("DELETE FROM $table");


My suggested recipe:


Create a 'junk' database
Save the above perl script as junk.pl.
Run junk.pl data1, and junk.pl data2, and junk.pl data3, etc. all at once, for as many CPU cores as your database server has, to start.  Open multiple shells and wrap each run in a Bash loop: while true; do date; junk.pl dataX; done. 


Watch your LSN grow, perhaps in another loop:

 silly# echo "SHOW INNODB STATUS \G" | mysql -p'xxxxxx' | grep '^Log seq'
 Log sequence number 124 3871092821
 silly# echo "SHOW INNODB STATUS \G" | mysql -p'xxxxxx' | grep '^Log seq'
 Log sequence number 124 4209892586
 silly# echo "SHOW INNODB STATUS \G" | mysql -p'xxxxxx' | grep '^Log seq'
 Log sequence number 125 85212387


The big number is an unsigned 32-bit INT which will wrap at 4GB, increasing the smaller number every time.  In this case above it just rolled from 124 to 125.  Your goal is hidden in the mysqld.log that sent you Googling for this ridiculous solution in the first place.  Once you cross that finish line, that's it!  Blow the horns!  Release the confetti!


  Sidebar: This uncovered an interesting bug in mysqld 5.0 w/REPEAT: if you go to 20 MB, it flips some internal counter and rolls over to ~ 96 KB.  No warning or error anywhere.  I wasn't about to waste time tracking that down.  10 MB works great.  If you do hit some other limit, it may complain.  I have various innodb buffers increased from default.  Season to taste.  As always, watch mysqld.log in one window.