Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
10.11.15
-
Server version: 10.11.5-MariaDB-1:10.11.5+maria~ubu1804-log source revision: 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c
-
Not for Release Notes
Description
MariaDB 10.11.5 crashed due to a fatal InnoDB error when attempting to read from a page in a non-existent or dropped tablespace. The log includes the sentinel space ID 4294967295, and a failing assertion in buf0lru.cc. This appears to be a race between a background purge and a DDL (e.g., DROP TABLE or TRUNCATE), or a bug related to page eviction.
Crash occurred under normal workload conditions (no DDL manually issued at the time). System uses innodb_file_per_table=ON, innodb_purge_threads=4, and has ~50G buffer pool on NVMe storage.
InnoDB: trying to read page [space=4294967295, page number=604711] in nonexisting or being-dropped tablespace
[FATAL] InnoDB: Unknown error Tablespace deleted or being deleted
...
Assertion failure in buf0lru.cc line 285:
InnoDB: Failing assertion: !block->page.in_file()
...
Thread pointer: 0x7f358800faa8
Attempting backtrace...
stack_bottom = 0x7f35c81ced18 thread_stack 0x49000
Can't start addr2line
...
mariadbd(handle_fatal_signal+0x555)
...
mysqld got signal 6 (SIGABRT)