This post focuses on the problem of the InnoDB log sequence number being in the future.
Preface: What is an InnoDB log sequence number?
The Log sequence number (LSN) is an important database parameter
used by InnoDB in many places.
The most important use is for crash recovery and buffer pool
purge control.
Internally, the InnoDB LSN counter never goes backward.
And, when InnoDB writes 50 bytes to the redo logs, the LSN
increases by 50 bytes.
As such we can count LSN in megabytes, gigabytes and etc.
Now for the problem: LSN being in the future!
When you have set innodb_force_recovery like this:
innodb_force_recovery=6
and then issue a data affecting query.
For example, if you are dropping a corrupted table after doing a mysqldump for backup …
[Read more]