Archive log prepare fails with InnoDB: Log sequence number at shutdown <nr> is lower than at startup <nr>!

Reported by George Ormond Lorch III on 2013-06-26
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup
Status tracked in 2.2
2.1
High
Vlad Lesin
2.2
High
Vlad Lesin

Bug Description

Using PS 5.6 trunk (revno 389) and ~vlad-lesin/percona-xtrabackup/2.1-apply-archived-logs-innodb5.6.

If I take an unprepared base backup and a handful of archive logs and execute:
xtrabackup --defaults-file=... --prepare --target-dir=... --innodb-log-arch-dir=...

It appears to go through the archived logs and apply them but xtrabackup completes with an error:
InnoDB: Log sequence number at shutdown 44866060 is lower than at startup 268472750!
InnoDB: Shutdown completed; log sequence number 44866060

It appears that log_sys->lsn is never updated to the recv_sys->recovered_lsn after the archive logs have been applied.

When you restart your server after copy back, no changes beyond 44866060 are visible.

description: updated
description: updated
Vlad Lesin (vlad-lesin) wrote :

Fixed in the last version of related branch. George, could you check it please?

tags: added: log-archiving
Alexey Kopytov (akopytov) wrote :

Did not appear in any released versions. Should go to "other bugs" in release notes.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers