Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
11.0.3
-
OpenSUSE 15.4
Description
After hitting this issue https://jira.mariadb.org/browse/MDEV-31579 and waiting for a fix in 11.0.3, I thought we were in the clear.
However, a couple of minutes into running 11.0.3, the server crashed, and now keeps crashing every few minutes.
2023-08-30 14:09:49 0x7fadf061e700 InnoDB: Assertion failure in file /home/abuild/rpmbuild/BUILD/mariadb-11.0.3/storage/innobase/btr/btr0cur.cc line 6702 |
InnoDB: Failing assertion: local_len >= BTR_EXTERN_FIELD_REF_SIZE
|
InnoDB: We intentionally generate a memory trap.
|
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ |
InnoDB: If you get repeated assertion failures or crashes, even
|
InnoDB: immediately after the mariadbd startup, there may be
|
InnoDB: corruption in the InnoDB tablespace. Please refer to
|
InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/ |
InnoDB: about forcing recovery.
|
230830 14:09:49 [ERROR] 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.
|
|
To report this bug, see https://mariadb.com/kb/en/reporting-bugs |
|
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. |
|
Server version: 11.0.3-MariaDB-log source revision: 70905bcb9059dcc40db3b73bc46a36c7d40f1e10 |
key_buffer_size=536870912 |
read_buffer_size=262144 |
max_used_connections=24 |
max_threads=2050 |
thread_count=22 |
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 5301930 K bytes of memory |
Hope that's ok; if not, decrease some variables in the equation. |
|
Thread pointer: 0x7fad3c000c58 |
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 = 0x7fadf061dd08 thread_stack 0x49000 |
/usr/sbin/mysqld(my_print_stacktrace+0x3d)[0x55ea4835712d] |
/usr/sbin/mysqld(handle_fatal_signal+0x575)[0x55ea47e60215] |
corrupted size vs. prev_size
|
Any idea what this crash is about?
Attachments
Issue Links
- blocks
-
MDEV-31443 assert [FATAL] InnoDB: Unable to find charset-collation for 254 after upgrade from 10.11.4 to 11.0
- Closed
-
MDEV-31579 Mariadb fails to start following automatic upgrade to 11.0.2 - Unable to find charset-collation for 271
- Closed
- relates to
-
MDEV-13542 Crashing on a corrupted page is unhelpful
- Closed
-
MDEV-32132 DROP INDEX followed by CREATE INDEX may corrupt data
- Closed
-
MDEV-29694 Remove the InnoDB change buffer
- Closed