Crash during InnoDB compression recovery

[monty solomon]

Started up a Percona 5.6 instance using a copy of an EBS snapshot of a Percona 5.6 instance that has compressed tables and got a crash due to assertion failure in file page0zip.cc line 3762

mysql Ver 14.14 Distrib 5.6.25-73.1, for Linux (x86_64) using 6.0
Server version: 5.6.25-73.1-log Percona Server (GPL), Release 73.1, Revision 07b797f
Linux misty-block 3.18.26-83.el6.x86_64 #1 SMP Mon Jan 25 18:39:22 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
CentOS release 6.7 (Final)

[monty solomon (monty+launchpad)]

InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 2 row operations to undo
InnoDB: Trx id counter is 52823434752
2016-06-02 19:01:34 26757 [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 2016-06-02 19:01:39 7ef761f0d700 InnoDB: Assertion failure in thread 139600965195520 in file page0zip.cc line 3762
InnoDB: Failing assertion: !*data
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.
19:01:39 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=67108864
read_buffer_size=1048576
max_used_connections=0
max_threads=502
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 = 715019 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
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x8cea7c]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x655fa1]
/lib64/libpthread.so.0(+0xf7e0)[0x7efda4ec27e0]
/lib64/libc.so.6(gsignal+0x35)[0x7efda351d625]
/lib64/libc.so.6(abort+0x175)[0x7efda351ee05]
/usr/sbin/mysqld[0x955753]
/usr/sbin/mysqld[0x9f974b]
/usr/sbin/mysqld[0x9322ad]
/usr/sbin/mysqld[0x9340bf]
/usr/sbin/mysqld[0xa18531]
/usr/sbin/mysqld[0xa63058]
/usr/sbin/mysqld[0x9b17a0]
/lib64/libpthread.so.0(+0x7aa1)[0x7efda4ebaaa1]
/lib64/libc.so.6(clone+0x6d)[0x7efda35d393d]
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.
160602 19:01:39 mysqld_safe mysqld from pid file /opt/mysql/dbprod/keywords-p0.pid ended
The server quit without updating PID file (/opt/mysql/dbpro[FAILED]ds-p0.pid).

[monty solomon (monty+launchpad)]

The bug status is still Undecided. Has this bug been triaged?

[monty solomon (monty+launchpad)]

The bug status is still New/Undecided. Has this bug been triaged?

[Shahriyar Rzayev (rzayev-sehriyar)]

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