Assertion failure in thread 139575177578240 in file log0recv.cc line 1237 Failing assertion: !page || (ibool)!!page_is_comp(page) == dict_table_is_comp(index->table)

[Ovais Tariq]

XtraBackup version 2.3.5

XtraBackup crashes during prepare stage:

InnoDB: Doing recovery: scanned up to log sequence number 7733658497066
2016-10-26 03:17:26 1 [Note] InnoDB: Starting an apply batch of log records to the database...
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 2016-10-26 03:18:43 7ef160e10700 InnoDB: Assertion failure in thread 139575177578240 in file log0recv.cc line 1237
InnoDB: Failing assertion: !page || (ibool)!!page_is_comp(page) == dict_table_is_comp(index->table)
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.
03:18:43 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. 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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=8194
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3276685 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

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 0x40000
mysqld(my_print_stacktrace+0x2c)[0x8c04ac]
mysqld(handle_fatal_signal+0x469)[0x6488c9]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0)[0x7efde17c18d0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7efddf6d9067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7efddf6da448]
mysqld[0x97071b]
mysqld[0x972b2f]
mysqld[0xa565ba]
mysqld[0xaa2850]
mysqld[0x9efeb0]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x80a4)[0x7efde17ba0a4]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7efddf78c87d]
You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.

[Ovais Tariq (ovais-tariq)]

I see a bug with a similar assertion fixed in 2.1.4: https://bugs.launchpad.net/percona-xtrabackup/+bug/1177206

[Sergei Glushchenko (sergei.glushchenko)]

It looks like datafile is corrupted. Which mysql version it belongs to?

[Ovais Tariq (ovais-tariq)]

MySQL 5.6. I don't think there was a corruption in the datafile. The base full backup would restore fine and a subsequent incremental backup also recovered fine. Unfortunately, I don't have the datafile handy.

[Shahriyar Rzayev (rzayev-sehriyar)]

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