xtrabackup segfaults during --prepare of certain FTS pages

[Robert Barabas]

Xtrabackup yields with -DWITH_DEBUG=FULL:

xtrabackup: starting shutdown with innodb_fast_shutdown = 0
15:18:31 UTC - xtrabackup got signal 11 ;
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: 0x20aff40
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
/backup/var/xtrabackup/percona-xtrabackup-2.2.11-Linux-x86_64/bin/xtrabackup(my_print_stacktrace+0x2e) [0x91a29e]
/backup/var/xtrabackup/percona-xtrabackup-2.2.11-Linux-x86_64/bin/xtrabackup(handle_fatal_signal+0x235) [0x81f195]
/lib/libpthread.so.0(+0xf510) [0x7fe045a90510]

GDB bt:

xtrabackup: starting shutdown with innodb_fast_shutdown = 0

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe62ef710 (LWP 20670)]
0x0000000000000000 in ?? ()
(gdb) bt
#0 0x0000000000000000 in ?? ()
#1 0x0000000000603540 in thd_supports_xa (thd=0x0) at /mnt/workspace/percona-xtrabackup-2.2-binary-tarball/label_exp/centos5-64/percona-xtrabackup-2.2.11/storage/innobase/handler/ha_innodb.cc:1267
#2 0x00000000005a63bd in trx_commit_for_mysql (trx=0x4903b88) at /mnt/workspace/percona-xtrabackup-2.2-binary-tarball/label_exp/centos5-64/percona-xtrabackup-2.2.11/storage/innobase/trx/trx0trx.cc:1624
#3 0x00000000006d4e69 in fts_sql_commit (trx=0x0) at /mnt/workspace/percona-xtrabackup-2.2-binary-tarball/label_exp/centos5-64/percona-xtrabackup-2.2.11/storage/innobase/fts/fts0sql.cc:345
#4 0x00000000006de0e5 in fts_sync_commit (sync=<optimized out>)
    at /mnt/workspace/percona-xtrabackup-2.2-binary-tarball/label_exp/centos5-64/percona-xtrabackup-2.2.11/storage/innobase/fts/fts0fts.cc:4388
#5 fts_sync (sync=0x4949330) at /mnt/workspace/percona-xtrabackup-2.2-binary-tarball/label_exp/centos5-64/percona-xtrabackup-2.2.11/storage/innobase/fts/fts0fts.cc:4472
#6 0x00000000006afa85 in fts_optimize_thread (arg=<optimized out>)
    at /mnt/workspace/percona-xtrabackup-2.2-binary-tarball/label_exp/centos5-64/percona-xtrabackup-2.2.11/storage/innobase/fts/fts0opt.cc:3092
#7 0x00007ffff7bc8547 in start_thread () from /lib/libpthread.so.0
#8 0x00007ffff62bc28d in clone () from /lib/libc.so.6

[Robert Barabas (robert-barabas)]

Replicated issue with xtrabackup 2.2.4, 2.2.10 and 2.2.11 (most recent version at the time of filing this issue).

[Robert Barabas (robert-barabas)]

Backup command was:

$ xtrabackup --defaults-file="/backup/var/lib/mysql/backup-my.cnf" --defaults-group="mysqld" --prepare --target-dir=/backup/var/lib/mysql --export --tmpdir=/tmp

Apply command was:
$ innobackupex --defaults-file=/tmp/ssync-my.cnf --socket=/tmp/mysql.sock --no-timestamp /backup/var/lib/mysql --host=localhost --no-lock

[Sergei Glushchenko (sergei.glushchenko)]

https://github.com/percona/percona-xtrabackup/pull/80

[Shahriyar Rzayev (rzayev-sehriyar)]

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