Hi there,
After having problems setting up replication between boxes, one of which had a system time which was completely wrong (which could be a red herring), I'm getting lots of log entries like this (_lots_):
100708 9:54:44 InnoDB: Error: page 20399 log sequence number 0 1888001665
InnoDB: is in the future! Current system log sequence number 0 9398936.
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.
100708 9:54:44 InnoDB: Error: page 204 log sequence number 0 1889563418
InnoDB: is in the future! Current system log sequence number 0 9398936.
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.
100708 9:54:44 InnoDB: Error: page 115 log sequence number 0 1889563467
InnoDB: is in the future! Current system log sequence number 0 9398936.
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.
Basically, I understand that there is some discrepancy between the innodb log files and the current lsn, and I've seen Heikki's advice regarding trying to fudge it by doing a mass load of inserts to artificially increase the lsn, but I'm finding that I'm going to have to do about 900 million inserts, and judging by my current tests, that's going to take a long long time. Is there any other way to offset the lsn to make it higher, or am I going to have to dump the data and re-import it on another server? It's a production box, so that's a big problem really!
Autocommit is on, and each innodb table is a separate ibd file.
Any advice gratefully received. Tom.
After having problems setting up replication between boxes, one of which had a system time which was completely wrong (which could be a red herring), I'm getting lots of log entries like this (_lots_):
100708 9:54:44 InnoDB: Error: page 20399 log sequence number 0 1888001665
InnoDB: is in the future! Current system log sequence number 0 9398936.
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.
100708 9:54:44 InnoDB: Error: page 204 log sequence number 0 1889563418
InnoDB: is in the future! Current system log sequence number 0 9398936.
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.
100708 9:54:44 InnoDB: Error: page 115 log sequence number 0 1889563467
InnoDB: is in the future! Current system log sequence number 0 9398936.
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.
Basically, I understand that there is some discrepancy between the innodb log files and the current lsn, and I've seen Heikki's advice regarding trying to fudge it by doing a mass load of inserts to artificially increase the lsn, but I'm finding that I'm going to have to do about 900 million inserts, and judging by my current tests, that's going to take a long long time. Is there any other way to offset the lsn to make it higher, or am I going to have to dump the data and re-import it on another server? It's a production box, so that's a big problem really!
Autocommit is on, and each innodb table is a separate ibd file.
Any advice gratefully received. Tom.