Bug #91629 corruption in the InnoDB
Submitted: 13 Jul 2018 14:12 Modified: 16 Jul 2018 18:02
Reporter: NOT_FOUND NOT_FOUND Email Updates:
Status: Unsupported Impact on me:
Category:MySQL Server: InnoDB storage engine Severity:S1 (Critical)
Version:8.0.11 for FreeBSD11.1 on i386 OS:FreeBSD (FreeBSD 11.2-RELEASE #0 r335510)
Assigned to: CPU Architecture:x86 (vortex i486)
Tags: innodb

[13 Jul 2018 14:12] NOT_FOUND NOT_FOUND
2018-07-13T14:02:46.458506Z 0 [System] [MY-010116] [Server] /usr/local/libexec/mysqld (mysqld 8.0.11) starting as process 7622
2018-07-13T14:03:01.682428Z 1 [ERROR] [MY-012097] [InnoDB] InnoDB: Table flags are a543afd in the data dictionary but the flags in file (null)  are bbafb794![FATAL]Table flags are 4800 in the data dictionary but the flags in file mysql.ibd  are 800!
2018-07-13T14:03:01.696607Z 1 [ERROR] [MY-000000] [InnoDB] InnoDB: Assertion failure: ut0ut.cc:675
InnoDB: thread 734086656
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/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
14:03:01 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.
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.

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

Thread pointer: 0x35bf8000
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 = bbafce70 thread_stack 0x36000

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 1

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.

How to repeat:
run /usr/local/bin/mysqld_safe
[16 Jul 2018 18:02] Miguel Solorzano
Thank you for the bug report. Please see https://www.mysql.com/support/supportedplatforms/database.html , for your OS only x86_64 is supported.