InnoDB: is in the future! errors after recovering one backup

[Miguel Angel Nieto]

After the --apply-log new log files are created. This is the error that we get after recovering the backup using those ib_logfiles:

[01/08/13 12:34:45] David Chapdelaine: # /etc/init.d/mysql start
 * Starting MySQL (Percona Server) database server mysqld [ OK ]
[01/08/13 12:35:09] David Chapdelaine: ]# cat /var/log/mysql/error.log
130801 19:34:35 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
130801 19:34:35 [ERROR] An old style --language value with language specific part detected: /usr/share/mysql/english/
130801 19:34:35 [ERROR] Use --lc-messages-dir without language specific part instead.
130801 19:34:35 [Note] Plugin 'FEDERATED' is disabled.
130801 19:34:35 InnoDB: The InnoDB memory heap is disabled
130801 19:34:35 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130801 19:34:35 InnoDB: Compressed tables use zlib 1.2.3
130801 19:34:35 InnoDB: Using Linux native AIO
130801 19:34:35 InnoDB: Initializing buffer pool, size = 256.0M
130801 19:34:35 InnoDB: Completed initialization of buffer pool
130801 19:34:35 InnoDB: highest supported file format is Barracuda.
130801 19:34:35 InnoDB: Restoring buffer pool pages from ib_lru_dump
130801 19:34:35 InnoDB: Waiting for the background threads to start
130801 19:34:36 Percona XtraDB (http://www.percona.com) 5.5.32-rel31.0 started; log sequence number 88330604556
130801 19:34:36 [Note] Event Scheduler: Loaded 0 events
130801 19:34:36 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.32-31.0-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Percona Server (GPL), Release 31.0
130801 19:34:38 InnoDB: Error: page 14389 log sequence number 88330613721
InnoDB: is in the future! Current system log sequence number 88330609227.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130801 19:34:38 InnoDB: Error: page 14390 log sequence number 88330791612
InnoDB: is in the future! Current system log sequence number 88330609227.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.

The error seems to be harmless and caused because during the recovery process XtraBackup also generates redo log records (e.g. when it has to perform a change buffer merge). That's why some pages get LSNs higher than the last LSN up to which recovery is performed.

We should find a way to avoid these errors, because they could make people think that the backup is not correct.

[Alexey Kopytov (akopytov)]

One way to fix this would be to disable all log writes during xtrabackup prepare.

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-890