Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've read several of the related topics posted here, but I have not been able to avoid this innodb error.

The steps I've taken to replicate data from a Slackware server - 5.5.27-log (S) to a FreeBSD slave - 5.5.21-log (F) were these:

  1. (S) flush tables with read lock;
  2. (S) in another terminal show master status;
  3. (S) stop mysqld via command line in third terminal;
  4. (F) while both servers are stopped, rsync mysql datadir from (S), excluding, mysql-bin and relay-* files; Also tried rsync of all files;
  5. (F) start mysqld (skip-slave)

121018 12:03:29 InnoDB: Error: page 7 log sequence number 456388912904 InnoDB: is in the future! Current system log sequence number 453905468629. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: InnoDB: for more information.

This kind of error happens for a lot of tables.

I know I can use dump, but the database is large, ca. 70GB and the systems are slow (old), so would like to get this replication to work with data transfer.

What should I try to solve this issue?

share|improve this question

Use Percona's hot backup utility Xtrabackup.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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