Restore fail
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
New
|
Undecided
|
Unassigned |
Bug Description
[03] Checking if there are indexes to rebuild in table uniwiserest/
FailedDocuments (space id: 126)
[03] Found index FK_RefSubmissio
[03] Found index FK_RefSubmissio
2017-03-27 18:26:06 0x7fe867ff7700 InnoDB: Assertion failure in thread 14063615
3935616 in file compact.cc line 821
InnoDB: Failing assertion: dict_foreign_
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.
18:26:06 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
xtrabackup(
xtrabackup(
/lib/x86_
/lib/x86_
/lib/x86_
xtrabackup[
xtrabackup[
/lib/x86_
/lib/x86_
Please report a bug at https:/
2017-03-
This command is run: file=/tmp/ restore/ backup- my.cnf - dir=/tmp/ restore/ --rebuild-indexes --rebuild-threads=8
xtrabackup --defaults-
-prepare --target-