MySQL Bugs: #96240: Crash loop during innodb recovery on startup

Bug #96240	Crash loop during innodb recovery on startup
Submitted:	18 Jul 2019 2:14	Modified:	22 Aug 2019 13:36
Reporter:	Guangbao Ni	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S3 (Non-critical)
Version:	5.6	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
InnoDB: Cannot insert index record DATA TUPLE: 2 fields;
 0: len 111; hex e4b88ae6b5b7e5b882e5a589e8b4a4e58cbae58c96e78e89e7aba5e8a385e5ba97202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020; asc                                                                                                                ;;
 1: len 8; hex 8000000004e75624; asc       V$;;

InnoDB: The table where this index record belongs
InnoDB: is now probably corrupt. Please run CHECK TABLE on
InnoDB: that table.
InnoDB: space 133, page 1777283, zip_size 0, bitmap bits 1
InnoDB: Submit a detailed bug report to http://bugs.mysql.com
18:41:36 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=3
max_threads=10513
thread_count=6
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 20355841 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
/u01/mysql_current/bin/mysqld(my_print_stacktrace+0x2c)[0x973cbc]
/u01/mysql_current/bin/mysqld(handle_fatal_signal+0x398)[0x6ae538]
/lib64/libpthread.so.0(+0xf5e0)[0x7fbd1fff85e0]
/u01/mysql_current/bin/mysqld[0x9d0332]
/u01/mysql_current/bin/mysqld[0x9bc26c]
/u01/mysql_current/bin/mysqld[0x9c5d3d]
/u01/mysql_current/bin/mysqld[0xaf7dc7]
/u01/mysql_current/bin/mysqld[0xb483dd]
/u01/mysql_current/bin/mysqld[0xa88cf8]
/lib64/libpthread.so.0(+0x7e25)[0x7fbd1fff0e25]
/lib64/libc.so.6(clone+0x6d)[0x7fbd1f0cf34d]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
Writing a core file
190717 02:41:38 mysqld_safe Number of processes running now: 0
190717 02:41:38 mysqld_safe mysqld restarted

How to repeat:
N/A

Percona hits the same issues before.

https://bugs.launchpad.net/percona-server/+bug/1269956

Hi Mr. Guangbao,

Thank you for your bug report.

However, we can not do anything with this report, since you have not provided us with sufficient info. Stacktrace is, for example, unusable.

Please, try to reproduce this error with our debug binary. Also , which binary are you using exactly and from which release ???

Last, we do not follow bug reports on the other forums ......

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".