undo_tablespaces.sh failures
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB | Status tracked in 2.4 | |||||
2.3 |
New
|
Undecided
|
Unassigned | |||
2.4 |
Fix Released
|
High
|
Sergei Glushchenko |
Bug Description
Test undo_tablespaces.sh sometimes fails with error:
InnoDB: Rollback of non-prepared transactions completed
2016-08-30 16:33:35 0x7fd60bfff700 InnoDB: Assertion failure in thread 140557301053184 in file buf0flu.cc line 3406
InnoDB: Failing assertion: srv_get_
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:33:35 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Thread pointer: 0x0
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 = 0 thread_stack 0x10000
/mnt/workspace/
/mnt/workspace/
/lib64/
/lib64/
/lib64/
/mnt/workspace/
/mnt/workspace/
/lib64/
/lib64/
Please report a bug at https:/
2016-08-30 16:33:35: run.sh: ===> innobackupex failed with exit code 2
------------
https:/ /github. com/percona/ percona- xtrabackup/ pull/252