King0770-Notes-InnoDB is in the future

Revision as of 21:47, 23 February 2011 by King0770 (talk | contribs) (Created page with '{{WIP}} If you look in the /opt/zimbra/log/mysql_error.log, and you see the following that looks like: <code><pre> 110224 4:38:44 InnoDB: Error: page 1 log sequence number 2…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


If you look in the /opt/zimbra/log/mysql_error.log, and you see the following that looks like:


110224  4:38:44  InnoDB: Error: page 1 log sequence number 252 1880879917
InnoDB: is in the future! Current system log sequence number 250 376589009.
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.
110224  4:38:44  InnoDB: Error: page 439 log sequence number 252 1829571000
InnoDB: is in the future! Current system log sequence number 250 376589009.
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.

You may need to increment the ib_logfiles. Basically, you need to find the large mboxgroupXX directly in ~/db/data that is equal, or greater in size to the size of ib_logfile0 and ib_logfile1. Once you have found a mboxgroup, you can create a temporary database, populate it with data from mail_item dump, then drop the table and database.


Example
-------

1) source ~/bin/zmshutil; zmsetvars

2) ~/mysql/bin/mysqldump mboxgroup10 -S $mysql_socket -u root --password=$mysql_root_password >> /tmp/mboxgroup10.sql

3) mysql -e "create database temp"

4) mysql temp < /tmp/mboxgroup10.sql

5) mysql -e "drop database temp"

I am not 100% this will work, but that suggestion came from a mysql post. http://forums.mysql.com/read.php?22,130164,131915#msg-131915

Jump to: navigation, search