Xtrabackup 2.2.5 fails with non-default innodb_log_block_size in 5.6.19
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
High
|
Sergei Glushchenko | ||
2.1 |
Won't Fix
|
Undecided
|
Unassigned | ||
2.2 |
Fix Released
|
High
|
Sergei Glushchenko | ||
2.3 |
Fix Released
|
High
|
Sergei Glushchenko |
Bug Description
Xtrabackup 2.2.5 fails in --apply-log stage throwing out this error:
InnoDB: Doing recovery: scanned up to log sequence number 14157798531072 (12%)
InnoDB: Doing recovery: scanned up to log sequence number 14157803773952 (12%)
InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 2014-10-22 11:59:39 7fd3571a9720 InnoDB: Assertion failure in thread 140545676187424 in file fil0fil.cc line 5655
InnoDB: Failing assertion: (len % OS_FILE_
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://
InnoDB: about forcing recovery.
16:59:39 UTC - xtrabackup got signal 6 ;
This could be because you hit a bug or data is corrupted.
This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
Thread pointer: 0x1765eb0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 1766ec0 thread_stack 0x10000
xtrabackup(
xtrabackup(
/lib64/
/lib64/
/lib64/
xtrabackup(
xtrabackup() [0x723237]
xtrabackup(
xtrabackup() [0x750697]
xtrabackup(
xtrabackup(
xtrabackup() [0x7521b5]
xtrabackup(
xtrabackup(
xtrabackup() [0x606fae]
xtrabackup() [0x60f6ba]
xtrabackup(
/lib64/
xtrabackup() [0x603fb9]
Please report a bug at https:/
innobackupex: Error:
innobackupex: ibbackup failed at /usr/bin/
backup-my.cnf file contents:
[mysqld]
innodb_
innodb_
innodb_
innodb_
innodb_
innodb_
innodb_
innodb_
innodb_
For what we can see in code in XB 2.2.5 it looks like there is an assertion in the file:
percona-
storage/
storage/
That is not present in 5.6.19 and recent Percona Server.
This bug looks like a regression from https:/
Related branches
- Alexey Kopytov (community): Approve
-
Diff: 29 lines (+4/-4)2 files modifiedstorage/innobase/fil/fil0fil.cc (+2/-2)
storage/innobase/os/os0file.cc (+2/-2)
- Alexey Kopytov (community): Approve
-
Diff: 29 lines (+4/-4)2 files modifiedstorage/innobase/fil/fil0fil.cc (+2/-2)
storage/innobase/os/os0file.cc (+2/-2)
Confirmed by code review. In current Percona Server 5.6.x code we have:
ut_a((len % OS_MIN_
assertions instead.