Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
10.11.8
-
None
-
Debian 12 , VMware
Description
On 2024-05-28 17:37:38 we had had critical outtage/fail of a cluster
|
0x7fc6e42ea6c0 InnoDB: Assertion failure in file ./storage/innobase/buf/buf0lru.cc line 281
|
|
InnoDB: Failing assertion: !block->page.in_file()
|
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.
|
240528 17:37:38 [ERROR] mysqld got signal 6 ;
|
Sorry, we probably made a mistake, and this is a bug.
|
Server version: 10.11.8-MariaDB-deb12-log source revision: 3a069644682e336e445039e48baae9693f9a08ee
|
key_buffer_size=67108864
|
read_buffer_size=524288
|
max_used_connections=26
|
max_threads=518
|
thread_count=27
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2466293 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
|
Thread pointer: 0x7fc6a4004ce8
|
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...
|
2024-05-28 17:37:38 1629 [Note] InnoDB: trying to read page [page id: space=4294967295, page number=1507] in nonexisting or being-dropped tablespace
|
2024-05-28 17:37:38 1629 [ERROR] [FATAL] InnoDB: Unknown error Tablespace deleted or being deleted
|