Assertion failure when preparing a backup

[Vasily Nemkov]

Preparing a backup with PXB 2.3 against MySQL 5.6.23 fails with an assertion failure:

InnoDB: Apply batch completed
InnoDB: 128 rollback segment(s) are active.
InnoDB: Waiting for purge to start
2017-11-16 08:51:24 7f429ffff700 InnoDB: Assertion failure in thread 139924128921344 in file fsp0fsp.cc line 1850
InnoDB: Failing assertion: inode
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
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://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
13:51:24 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
/mnt/workspace/percona-xtrabackup-2.3-param-light/Host/xb-centos7-64/storage/innobase/xtrabackup/src/xtrabackup(my_print_stacktrace+0x2e) [0x96fcce]
/mnt/workspace/percona-xtrabackup-2.3-param-light/Host/xb-centos7-64/storage/innobase/xtrabackup/src/xtrabackup(handle_fatal_signal+0x262) [0x722c82]
/lib64/libpthread.so.0(+0xf5e0) [0x7f42cb7955e0]
/lib64/libc.so.6(gsignal+0x37) [0x7f42c9eff1f7]
/lib64/libc.so.6(abort+0x148) [0x7f42c9f008e8]
/mnt/workspace/percona-xtrabackup-2.3-param-light/Host/xb-centos7-64/storage/innobase/xtrabackup/src/xtrabackup() [0x56fe79]
/mnt/workspace/percona-xtrabackup-2.3-param-light/Host/xb-centos7-64/storage/innobase/xtrabackup/src/xtrabackup() [0x5fc6f9]
/mnt/workspace/percona-xtrabackup-2.3-param-light/Host/xb-centos7-64/storage/innobase/xtrabackup/src/xtrabackup() [0x666060]
/mnt/workspace/percona-xtrabackup-2.3-param-light/Host/xb-centos7-64/storage/innobase/xtrabackup/src/xtrabackup(trx_purge(unsigned long, unsigned long, bool)+0x838) [0x6672e8]
/mnt/workspace/percona-xtrabackup-2.3-param-light/Host/xb-centos7-64/storage/innobase/xtrabackup/src/xtrabackup(srv_purge_coordinator_thread+0x557) [0x6025a7]
/lib64/libpthread.so.0(+0x7e25) [0x7f42cb78de25]
/lib64/libc.so.6(clone+0x6d) [0x7f42c9fc234d]

Please report a bug at https://bugs.launchpad.net/percona-xtrabackup
2017-11-16 08:51:24: run.sh: ===> xtrabackup failed with exit code 1

Here is how PXB invoked:
xtrabackup --defaults-file=/home/enmk/proj/pxb-2.3/storage/innobase/xtrabackup/test/var/w1/var1/my.cnf --no-version-check --prepare --target-dir=/home/enmk/proj/pxb-2.3/storage/innobase/xtrabackup/test/var/w1/var1/backup_50Mb

$ xtrabackup --version
xtrabackup version 2.3.9 based on MySQL server 5.6.24 Linux (x86_64) (revision id: 0868728)

See for details: http://jenkins.percona.com/view/PXB%202.3/job/percona-xtrabackup-2.3-param-light/36/

[Vasily Nemkov (vasily.nemkov)]

Reproducible with PXB 2.3.7 from Ubuntu Xenial software repository.

[Sergei Glushchenko (sergei.glushchenko)]

It turned out to be a bug in the test case. Incremental backup was applied on top of the fully prepared one. xtrabackup in turn should not even try to apply incremental in this case. Lets fix both issues.

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-515