Apply log fails with transaction log corruption reported on 2.4.1
Bug #1561053 reported by
Przemek
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Percona XtraBackup moved to https://jira.percona.com/projects/PXB | Status tracked in 2.4 | |||||
| 2.4 |
New
|
Undecided
|
Unassigned | |||
Bug Description
Backup taken from system with multi TB data, during ongoing high concurrent load on the server. No errors for backup stage, but apply-log fails with the error:
xtrabackup: error: The transaction log file is corrupted.
xtrabackup: error: The log was not applied to the intended LSN!
xtrabackup: Log applied to lsn 94732613309427
xtrabackup: The intended lsn is 94752871632337
Full apply log in attachment.
Backuped server version: PS 5.6.21, Xtrabackup version 2.4.1.
Revision history for this message
| Przemek (pmalkowski) wrote | #1 |
Revision history for this message
| Sergei Glushchenko (sergei.glushchenko) wrote | #2 |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #3 |
To post a comment you must log in.
Just to note, the issue seems to be few lines above: " Log block 341041643 at lsn 94732613309440 has valid header, but checksum field contains 1021286565, should be 1391750493"