Archive log prepare fails with InnoDB: Log sequence number at shutdown <nr> is lower than at startup <nr>!
Bug #1195055 reported by
George Ormond Lorch III
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
High
|
Vlad Lesin | ||
| 2.1 |
Fix Released
|
High
|
Vlad Lesin | ||
| 2.2 |
Fix Released
|
High
|
Vlad Lesin | ||
Bug Description
Using PS 5.6 trunk (revno 389) and ~vlad-lesin/
If I take an unprepared base backup and a handful of archive logs and execute:
xtrabackup --defaults-file=... --prepare --target-dir=... --innodb-
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-
When you restart your server after copy back, no changes beyond 44866060 are visible.
Related branches
lp:~vlad-lesin/percona-xtrabackup/2.1-apply-archived-logs-innodb5.6
- Alexey Kopytov (community): Approve
- Laurynas Biveinis (community): Needs Fixing
-
Diff: 1525 lines (+1383/-17)3 files modifiedpatches/innodb56.patch (+822/-0)
src/xtrabackup.cc (+172/-17)
test/t/xb_apply_archived_logs.sh (+389/-0)
| description: | updated |
| description: | updated |
Revision history for this message
| Vlad Lesin (vlad-lesin) wrote | #1 |
| tags: | added: log-archiving |
Revision history for this message
| Alexey Kopytov (akopytov) wrote | #2 |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #3 |
To post a comment you must log in.
Fixed in the last version of related branch. George, could you check it please?