xtrabackup crashed during apply 5.5 backup set with utf8_general50_ci collation - fix not working

[Sven]

Bugfix described in https://bugs.launchpad.net/percona-xtrabackup/+bug/1533722 looks not like working. . When preparing a full backup i get following error:

InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72
 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: xtrabackup: Last MySQL binlog file position 81139224, file name /var/log/mysql/n1/mysql-bin.049791
InnoDB: Starting in background the rollback of uncommitted transactions
InnoDB: Rolling back trx with id 14012823469, 1493070 rows to undo

InnoDB: Progress in percents: 1InnoDB: Creating shared tablespace for temporary tables
InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
xtrabackup: Character set '#253' is not a compiled character set and is not specified in the '/usr/share/charsets/Index.xml' file
[FATAL] InnoDB: Unable to find charset-collation 253
2017-12-11 11:00:05 0x7f99711a6700 InnoDB: Assertion failure in thread 140297004279552 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.
10:00:05 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...
InnoDB: File './ibtmp1' size is now 12 MB.
InnoDB: 96 redo rollback segment(s) found. 1 redo rollback segment(s) are active.
InnoDB: 32 non-redo rollback segment(s) are active.
InnoDB: page_cleaner: 1000ms intended loop took 1015922ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)
InnoDB: 5.7.13 started; log sequence number 127652818707695
InnoDB: Unknown collation 253.
InnoDB: Unknown collation 253.
InnoDB: Unknown collation 253.
stack_bottom = 0 thread_stack 0x10000
/usr/bin/xtrabackup(my_print_stacktrace+0x2c)[0xc940fc]
/usr/bin/xtrabackup(handle_fatal_signal+0x261)[0xa46531]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f9992570890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f999020e067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f999020f448]
/usr/bin/xtrabackup[0x6f96bb]
/usr/bin/xtrabackup(_ZN2ib5fatalD1Ev+0x15d)[0x81c3fd]
/usr/bin/xtrabackup[0x91fb2c]
/usr/bin/xtrabackup(_Z29cmp_dtuple_rec_with_match_lowPK8dtuple_tPKhPKmmPm+0x205)[0x9202d5]
/usr/bin/xtrabackup(_Z26page_cur_search_with_matchPK11buf_block_tPK12dict_index_tPK8dtuple_t15page_cur_mode_tPmS9_P10page_cur_tP8rtr_info+0x1da)[0x905ffa]
/usr/bin/xtrabackup(_Z27btr_cur_search_to_nth_levelP12dict_index_tmPK8dtuple_t15page_cur_mode_tmP9btr_cur_tmPKcmP5mtr_t+0xefa)[0x7dff0a]
/usr/bin/xtrabackup(_Z22row_search_index_entryP12dict_index_tPK8dtuple_tmP10btr_pcur_tP5mtr_t+0x106)[0x936836]
/usr/bin/xtrabackup[0xd20e1c]
/usr/bin/xtrabackup(_Z12row_undo_modP11undo_node_tP9que_thr_t+0x5d7)[0xd238f7]
/usr/bin/xtrabackup(_Z13row_undo_stepP9que_thr_t+0x67)[0xd1c7c7]
/usr/bin/xtrabackup(_Z15que_run_threadsP9que_thr_t+0x719)[0x8c5b99]
/usr/bin/xtrabackup(_Z31trx_rollback_or_clean_recoveredm+0xcdd)[0x8fcd2d]
/usr/bin/xtrabackup(trx_rollback_or_clean_all_recovered+0xe)[0x8fdfce]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f9992569064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f99902c162d]

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

[Vasily Nemkov (vasily.nemkov)]

Hi, Could you please specify a version of xtrabackup you are using ?

[Sven (rapidsven)]

Hi, it's the latest, 2.4.9-1

[Shahriyar Rzayev (rzayev-sehriyar)]

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