Comment 2 for bug 1203668

So, I was able to get following backtrace on trunk build of PXC:

0x7e2dbc my_print_stacktrace + 44
0x6ae3b1 handle_fatal_signal + 1185
0x7fa51c38f0e0 _end + 456080384
0x7fa51bf6b66c _end + 451740044
0x8998d9 buf_page_is_corrupted + 1209
0x8dd353 fil_check_first_page + 211
0x8e21dd fil_read_first_page + 381
0x84c51a innobase_start_or_create_for_mysql + 3978
0x7fb395 innobase_init(void*) + 2853
0x6b0608 ha_initialize_handlerton(st_plugin_int*) + 72
0x5b4460 plugin_initialize(st_plugin_int*) + 96
0x5b8239 plugin_init(int*, char**, int) + 2073
0x5314b1 init_server_components() + 657
0x5365f1 mysqld_main(int, char**) + 2065
0x7fa51a914a15 _end + 428315957
0x52bc9d _start + 41

However, this is same as the multi ibdata1 regression's backtrace.

Next, I tried a build from lp:~percona-core/percona-xtradb-cluster/percona-xtradb-cluster-for-xtrabackup-tests/

and it passed.

=====================

./run.sh -d /pxc -t t/bug891496.sh
Detecting server version...
Running against Percona Server 5.5.31-23.7.5-log (XtraDB 5.5.31-rel30.3)
Using 'xtrabackup_55' as xtrabackup binary
Using 8 parallel workers

==============================================================================
TEST WORKER RESULT TIME(s) or COMMENT
------------------------------------------------------------------------------
bug891496 w1 [passed] 25
==============================================================================
Spent 25 of 30 seconds executing testcases

SUMMARY: 1 run, 1 successful, 0 skipped, 0 failed

See results/ for detailed output

==============

(I used binaries from http://jenkins.percona.com/job/percona-xtrabackup-2.1-binaries/label_exp=centos6-64/ for this)

Hence, I suspect an old 5.5.32 build (and not lp:~percona-core/percona-xtradb-cluster/percona-xtradb-cluster-for-xtrabackup-tests/
) may have been used/caused for this crash.