Bug #107968 MySQL crashes with InnoDB errors
Submitted: 26 Jul 2022 2:36 Modified: 26 Jul 2022 14:24
Reporter: Glen Loren Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version: OS:Debian
Assigned to: CPU Architecture:x86

[26 Jul 2022 2:36] Glen Loren
I'm running MySQL on a Debian distro. Recently it crashed and won't start. Here is the log file:

220725 18:13:03 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
220725 18:13:03 [Note] Plugin 'FEDERATED' is disabled.
220725 18:13:03 InnoDB: The InnoDB memory heap is disabled
220725 18:13:03 InnoDB: Mutexes and rw_locks use GCC atomic builtins
220725 18:13:03 InnoDB: Compressed tables use zlib 1.2.8
220725 18:13:03 InnoDB: Using Linux native AIO
220725 18:13:03 InnoDB: Initializing buffer pool, size = 128.0M
220725 18:13:03 InnoDB: Completed initialization of buffer pool
220725 18:13:03 InnoDB: highest supported file format is Barracuda.
InnoDB: Error: tried to read 65536 bytes at offset 0 125952.
InnoDB: Was only able to read 1024.
InnoDB: Fatal error: cannot read from file. OS error number 17.
220725 18:13:24  InnoDB: Assertion failure in thread 140443736074048 in file os0file.c line 2549
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
23:13:24 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.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346701 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 0x30000
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:
[26 Jul 2022 14:24] MySQL Verification Team
Hi Mr. Loren,

Thank you for your bug report.

However, this seems like an error in the I/O, which can be either a hardware error or OS error.

If you think otherwise, then please do send us a fully repeatable test case, so that we can reproduce the assertion.

Read about it further on.

Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php 

If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.  

Thank you for your interest in MySQL.