xtrabackup 2.3.2 crash --prepare

[Julian]

I am using xtrabackup for quite a while now on Percona Server 5.5 and it always worked great.

I am now trying to use it (percona-xtrabackup-2.3.2-1.el7) with MariaDB 10.1.8 and it fails on --prepare.
Unfortunately it gives me no hint what I am doing wrong or where i can have a look at.

xtrabackup --defaults-file=/etc/my.cnf.d/xtrabackup.cnf --prepare --target-dir=/var/backup//mysql/2015-12-09_15-30

I get this error on prepare:

xtrabackup version 2.3.2 based on MySQL server 5.6.24 Linux (x86_64) (revision id: 306a2e0)
xtrabackup: cd to /var/backup//mysql/2015-12-09_15-42
xtrabackup: This target seems to be not prepared yet.
xtrabackup: xtrabackup_logfile detected: size=2097152, start_lsn=(12234964)
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 2097152
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 2097152
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
InnoDB: Using atomics to ref count buffer pool pages
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Memory barrier is not used
InnoDB: Compressed tables use zlib 1.2.7
InnoDB: Not using CPU crc32 instructions
InnoDB: Initializing buffer pool, size = 100.0M
InnoDB: Completed initialization of buffer pool
InnoDB: Highest supported file format is Barracuda.
InnoDB: The log sequence numbers 1616819 and 1616819 in ibdata files do not match the log sequence number 12234964 in the ib_logfiles!
InnoDB: Database was not shutdown normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages
InnoDB: from the doublewrite buffer...
InnoDB: 128 rollback segment(s) are active.
InnoDB: Waiting for purge to start
14:42:08 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: 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(my_print_stacktrace+0x2e) [0x927d2e]
xtrabackup(handle_fatal_signal+0x262) [0x7214b2]
/lib64/libpthread.so.0(+0xf130) [0x7fd974cc9130]
xtrabackup(trx_undo_update_rec_get_update(unsigned char*, dict_index_t*, unsigned long, unsigned long, unsigned long, unsigned long, trx_t*, mem_block_info_t*, upd_t**)+0x590) [0x6c37b0]
xtrabackup(row_purge_step(que_thr_t*)+0x3bc) [0x69836c]
xtrabackup(que_run_threads(que_thr_t*)+0x498) [0x988a68]
xtrabackup(trx_purge(unsigned long, unsigned long, bool)+0x776) [0x604346]
xtrabackup(srv_purge_coordinator_thread+0x27f) [0x6d80bf]
/lib64/libpthread.so.0(+0x7df5) [0x7fd974cc1df5]
/lib64/libc.so.6(clone+0x6d) [0x7fd9734f71ad]

Please report a bug at https://bugs.launchpad.net/percona-xtrabackup

[Sergei Glushchenko (sergei.glushchenko)]

Hi Julian,

Any MariaDB specific features that you are using? Maybe compression

https://mariadb.com/kb/en/mariadb/compression/

or encryption

https://blog.mariadb.org/table-and-tablespace-encryption-on-mariadb-10-1-3/

?

[Julian (kont6kt)]

Hi Sergei.,

The Server is started with default config without configuration.

show global variables like 'innodb_compression_algorithm';
+------------------------------+-------+
| Variable_name | Value |
+------------------------------+-------+
| innodb_compression_algorithm | none |
+------------------------------+-------+

Encryption is not used.

[Sergei Glushchenko (sergei.glushchenko)]

This stack trace looks similar to https://mariadb.atlassian.net/browse/MDEV-9177. Apparently there is a bug in MariaDB 10.1.8. There is an option to upgrade to 10.1.9.

[Julian (kont6kt)]

Hey,

Just to be clear: xtrabackup is throwing this error, not Mariadb.

I understand you correctly that MariaDB somehow "corrupted" the data-files and now xtrabackup can´t work with them?

[Sergei Glushchenko (sergei.glushchenko)]

Yes, it might be a case. At least stack trace looks exactly the same as the on in the MariaDB's bug report. So, not only xtrabackup wont work with the data, but also 10.1.9 will not work. Would be awesome if you could confirm that.

[Launchpad Janitor (janitor)]

[Expired for Percona XtraBackup because there has been no activity for 60 days.]

[Shahriyar Rzayev (rzayev-sehriyar)]

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