Xtrabackup 2.0.7 or 2.1.2 failed: expected log block no. 5458041, but got no. 1070811265 from the log file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
High
|
Alexey Kopytov | ||
2.0 |
Fix Released
|
High
|
Alexey Kopytov | ||
2.1 |
Fix Released
|
High
|
Alexey Kopytov | ||
2.2 |
Fix Released
|
High
|
Alexey Kopytov |
Bug Description
Affected versions:
percona-
percona-
xtrabackup version 2.0.7 for Percona Server 5.1.59 unknown-linux-gnu (x86_64) (revision id: 552)
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /database/mysql
xtrabackup: Target instance is assumed as followings.
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: using O_DIRECT
InnoDB: Warning: allocated tablespace 424, old maximum was 9 ...
xtrabackup: error: log block numbers mismatch:
xtrabackup: error: expected log block no. 5458041, but got no. 1070811265 from the log file.
xtrabackup: Error: xtrabackup_
innobackupex: Error: ibbackup child process has died at /usr/bin/
The error emitted after 179m45.411s since backup start.
Before backup start transaction log information:
Log sequence number 186856561401671
Log flushed up to 186856559716066
Last checkpoint at 186854266314745
Max checkpoint age 3476324967
Checkpoint age target 3367689812
Modified age 2265855030
Checkpoint age 2295086926
0 pending log writes, 0 pending chkp writes
1019036192 log i/o's done, 220.02 log i/o's/second
Right after xtrabackup crash:
Log sequence number 186919780065548
Log flushed up to 186919776998233
Last checkpoint at 186917463665464
Max checkpoint age 3476324967
Checkpoint age target 3367689812
Modified age 2313548226
Checkpoint age 2316400084
0 pending log writes, 0 pending chkp writes
1020869843 log i/o's done, 88.32 log i/o's/second
There are several errors from previous runs:
xtrabackup: error: expected log block no. 3388077, but got no. 1068741301 from the log file.
>> log scanned up to (183619734185080)
>> log scanned up to (183619741409546)
xtrabackup: error: log block numbers mismatch:
xtrabackup: error: expected log block no. 2551941, but got no. 1067905165 from the log file.
From previous month innodb recovery information:
130618 23:46:21 Percona XtraDB (http://
As you can see block no. diff is always 1065353224 compare to much smaller LSN change:
(18691978006554
Related branches
- Alexey Kopytov (community): Approve
-
Diff: 19 lines (+7/-2)1 file modifiedsrc/xtrabackup.cc (+7/-2)
- Alexey Kopytov (community): Approve
-
Diff: 19 lines (+7/-2)1 file modifiedsrc/xtrabackup.cc (+7/-2)
- Percona core: Pending requested
-
Diff: 39 lines (+10/-10)1 file modifiedsrc/xtrabackup.cc (+10/-10)
- Percona core: Pending requested
-
Diff: 27 lines (+4/-4)1 file modifiedsrc/xtrabackup.cc (+4/-4)
description: | updated |
summary: |
- Xtrabackup 2.0.7 failed: expected log block no. 5458041, but got no. - 1070811265 from the log file + Xtrabackup 2.0.7 or 2.1.2 failed: expected log block no. 5458041, but + got no. 1070811265 from the log file |
tags: | added: i33538 |
Changed in percona-xtrabackup: | |
status: | Incomplete → New |
Please provide the InnoDB log configuration from the server.