InnoDB: 96 redo rollback segment(s) found. 1 redo rollback segment(s) are active.
InnoDB: 32 non-redo rollback segment(s) are active.
InnoDB: Waiting for purge to start
InnoDB: 5.7.10 started; log sequence number 452498965
xtrabackup: starting shutdown with innodb_fast_shutdown = 1
InnoDB: not started
InnoDB: FTS optimize thread exiting.
InnoDB: Starting shutdown...
2016-01-21 05:22:29 0x7efdd8bf7700 InnoDB: Assertion failure in thread 139628728252160 in file fsp0fsp.cc line 2986
InnoDB: Failing assertion: size == space->size_in_header
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
05:22:29 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might 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
../src/xtrabackup(my_print_stacktrace+0x35)[0x14a5e1d]
../src/xtrabackup(handle_fatal_signal+0x2ab)[0x135db2d]
/lib64/libpthread.so.0(+0xf130)[0x7efde8fbf130]
/lib64/libc.so.6(gsignal+0x37)[0x7efde75245d7]
/lib64/libc.so.6(abort+0x148)[0x7efde7525cc8]
../src/xtrabackup[0xf2edef]
../src/xtrabackup(_Z24fsp_reserve_free_extentsPmmm13fsp_reserve_tP5mtr_tm+0xfa)[0xe22968]
../src/xtrabackup(_Z26btr_cur_pessimistic_deleteP7dberr_tmP9btr_cur_tmbP5mtr_t+0x29d)[0xe6e10b]
../src/xtrabackup[0x151823d]
../src/xtrabackup[0x151895b]
../src/xtrabackup[0x1518ccc]
../src/xtrabackup[0x151965e]
../src/xtrabackup[0x15197ae]
../src/xtrabackup(_Z14row_purge_stepP9que_thr_t+0x17f)[0x1519a6e]
../src/xtrabackup[0xf161a5]
../src/xtrabackup[0xf163a4]
../src/xtrabackup(_Z15que_run_threadsP9que_thr_t+0x92)[0xf1655a]
../src/xtrabackup(_Z9trx_purgemmb+0x2de)[0x10b53bb]
../src/xtrabackup(srv_purge_coordinator_thread+0x2d0)[0xfcc49a]
/lib64/libpthread.so.0(+0x7df5)[0x7efde8fb7df5]
/lib64/libc.so.6(clone+0x6d)[0x7efde75e51ad]
Prepare fails the same way without compression:
InnoDB: 96 redo rollback segment(s) found. 1 redo rollback segment(s) are active. fast_shutdown = 1 size_in_ header bugs.mysql. com. dev.mysql. com/doc/ refman/ 5.7/en/ forcing- innodb- recovery. html
InnoDB: 32 non-redo rollback segment(s) are active.
InnoDB: Waiting for purge to start
InnoDB: 5.7.10 started; log sequence number 452498965
xtrabackup: starting shutdown with innodb_
InnoDB: not started
InnoDB: FTS optimize thread exiting.
InnoDB: Starting shutdown...
2016-01-21 05:22:29 0x7efdd8bf7700 InnoDB: Assertion failure in thread 139628728252160 in file fsp0fsp.cc line 2986
InnoDB: Failing assertion: size == space->
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.
05:22:29 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Thread pointer: 0x0 xtrabackup( my_print_ stacktrace+ 0x35)[0x14a5e1d ] xtrabackup( handle_ fatal_signal+ 0x2ab)[ 0x135db2d] libpthread. so.0(+0xf130) [0x7efde8fbf130 ] libc.so. 6(gsignal+ 0x37)[0x7efde75 245d7] libc.so. 6(abort+ 0x148)[ 0x7efde7525cc8] xtrabackup[ 0xf2edef] xtrabackup( _Z24fsp_ reserve_ free_extentsPmm m13fsp_ reserve_ tP5mtr_ tm+0xfa) [0xe22968] xtrabackup( _Z26btr_ cur_pessimistic _deleteP7dberr_ tmP9btr_ cur_tmbP5mtr_ t+0x29d) [0xe6e10b] xtrabackup[ 0x151823d] xtrabackup[ 0x151895b] xtrabackup[ 0x1518ccc] xtrabackup[ 0x151965e] xtrabackup[ 0x15197ae] xtrabackup( _Z14row_ purge_stepP9que _thr_t+ 0x17f)[ 0x1519a6e] xtrabackup[ 0xf161a5] xtrabackup[ 0xf163a4] xtrabackup( _Z15que_ run_threadsP9qu e_thr_t+ 0x92)[0xf1655a] xtrabackup( _Z9trx_ purgemmb+ 0x2de)[ 0x10b53bb] xtrabackup( srv_purge_ coordinator_ thread+ 0x2d0)[ 0xfcc49a] libpthread. so.0(+0x7df5) [0x7efde8fb7df5 ] libc.so. 6(clone+ 0x6d)[0x7efde75 e51ad]
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
../src/
../src/
/lib64/
/lib64/
/lib64/
../src/
../src/
../src/
../src/
../src/
../src/
../src/
../src/
../src/
../src/
../src/
../src/
../src/
../src/
/lib64/
/lib64/
Please report a bug at https:/ /bugs.launchpad .net/percona- xtrabackup
Assertion is DEBUG only