Bug #76289 Database page corruption on disk or a failed
Submitted: 12 Mar 2015 12:29 Modified: 3 Apr 2018 2:18
Reporter: NRIFT Sysadmin Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:5.6.14 OS:Linux
Assigned to: CPU Architecture:Any

[12 Mar 2015 12:29] NRIFT Sysadmin
Description:
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 138400.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
2015-03-10 13:37:29 4d67e940  InnoDB: Assertion failure in thread 1298655552 in file buf0buf.cc line 4054
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.
08:07:29 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.

key_buffer_size=67108864
read_buffer_size=2097152
max_used_connections=190
max_threads=1000
thread_count=119
connection_count=119
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2639184 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

How to repeat:
N/A
[3 Mar 2018 2:18] Miguel Solorzano
It's still an issue for you or using recent release version isn't more repeatable?. We can't repeat since not test case was provide, Thanks in advance.
[4 Apr 2018 1:00] Bugs System
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".