PXB Table flags mismatch on stats with tables filter against MariaDB database with partitioned tables
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB | Status tracked in 2.4 | |||||
2.3 |
Triaged
|
Low
|
Unassigned | |||
2.4 |
Triaged
|
Low
|
Unassigned |
Bug Description
PXB 2.3.8 was tested against the MariaDB 10.1.2, resulting in several tests failing with the same symptoms:
ib_part_include
ib_
PXB crashes when invoked with --stats and --tables (or --tables-file) producing following output:
InnoDB: Error: table flags are 0x400 in the data dictionary
InnoDB: but the flags in file ./test/
2017-05-16 14:59:22 7fd2eb047740 InnoDB: Assertion failure in thread 140543862798144 in file fil0fil.cc line 624
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.
11:59:22 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: 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
/home/enmk/
/home/enmk/
/lib/x86_
/lib/x86_
/lib/x86_
/home/enmk/
/home/enmk/
/home/enmk/
/home/enmk/
/home/enmk/
/home/enmk/
/home/enmk/
/home/enmk/
/home/enmk/
/home/enmk/
/home/enmk/
/home/enmk/
/home/enmk/
/home/enmk/
/lib/x86_
/home/enmk/
Probably only affects partitioned tables.