PXB2.3 crashes during prepare of incremental backup

[Phil Schroeder]

InnoDB: Doing recovery: scanned up to log sequence number 36433385491968 (99%)
InnoDB: Doing recovery: scanned up to log sequence number 36433385954702 (99%)
InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 2017-11-02 20:51:38 7feda0b0d700 InnoDB: Assertion failure in thread 140658579920640 in file rem0rec.cc line 577
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
20:51:38 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.
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
innobackupex(my_print_stacktrace+0x3d) [0x964acd]
innobackupex(handle_fatal_signal+0x281) [0x824e61]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11390) [0x7feec9528390]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38) [0x7feec76fb428]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a) [0x7feec76fd02a]
innobackupex(rec_get_offsets_func(unsigned char const*, dict_index_t const*, unsigned long*, unsigned long, mem_block_info_t**)+0x56) [0x636ba6]
innobackupex(page_cur_parse_insert_rec(unsigned long, unsigned char*, unsigned char*, buf_block_t*, dict_index_t*, mtr_t*)+0x2b6) [0x69f916]
innobackupex() [0x60d954]
innobackupex(recv_recover_page_func(unsigned long, buf_block_t*)+0x5ae) [0x60f9ae]
innobackupex(buf_page_io_complete(buf_page_t*)+0x250) [0x61a8e0]
innobackupex(fil_aio_wait(unsigned long)+0x198) [0x5e72c8]
innobackupex(io_handler_thread+0x28) [0x5d4c18]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba) [0x7feec951e6ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7feec77cd3dd]

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

[Sergei Glushchenko (sergei.glushchenko)]

Does it crash on every backup or only some of them? Which exact PXB version is it? Which MySQL version?

[Phil Schroeder (pschroeder)]

We can close this report...I found that this may have been happening because the full backup was taken while innodb_track_page_changes was off, and the incrementals were run while that value was true. I've since taken a full backup with that flag set, and the incrementals are no longer dying this way.

[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-1478