Comment 4 for bug 1653545

170508 07:43:10 >> log scanned up to (5464322826085)
InnoDB: Last flushed lsn: 5463932380446 load_index lsn 5464322854907
[FATAL] InnoDB: An optimized(without redo logging) DDLoperation has been performed. All modified pages may not have been flushed to the disk yet.
    PXB will not be able take a consistent backup. Retry the backup operation
2017-05-08 07:43:11 0x7f548ff82700 InnoDB: Assertion failure in thread 140001169385216 in file ut0ut.cc line 916
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.
07:43:12 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
innobackupex(my_print_stacktrace+0x35)[0xebe3d5]
innobackupex(handle_fatal_signal+0x273)[0xa1a733]
/lib64/libpthread.so.0[0x3eb000f7e0]
/lib64/libc.so.6(gsignal+0x35)[0x3eafc32625]
/lib64/libc.so.6(abort+0x175)[0x3eafc33e05]
innobackupex(_Z21btr_corruption_reportPK11buf_block_tPK12dict_index_t+0x0)[0x7318b0]
innobackupex(_ZN2ib5fatalD1Ev+0xb3)[0x81afb3]
innobackupex[0x796801]
innobackupex(_Z19recv_parse_log_recsm7store_tb+0x4df)[0x79944f]
innobackupex[0x73bc00]
innobackupex[0x73c216]
innobackupex[0x73c5c3]
/lib64/libpthread.so.0[0x3eb0007aa1]
/lib64/libc.so.6(clone+0x6d)[0x3eafce893d]