[MDEV-32267] InnoDB: Assertion failure in thread 139669830482048 in file fsp0fsp.c line 2877 Created: 2023-09-27  Updated: 2023-10-30  Resolved: 2023-10-30

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 5.5
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Alvaro Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None

Attachments: Zip Archive mariadb.zip    

 Description   

mysqld not starting, giving error [ERROR] mysqld got signal 6 ;

ibdata1 file corrupted, appeared as empty.

Adding mariadb.log for more information

 Comments   
Comment by Marko Mäkelä [ 2023-09-27 ]

In mariadb.zip I see that crash recovery had been invoked before the assertion failure:

mariadb-5.5.68

 
230927 11:39:43 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 27500 ...
 
230927 11:39:43 InnoDB: The InnoDB memory heap is disabled
 
230927 11:39:43 InnoDB: Mutexes and rw_locks use GCC atomic builtins
 
230927 11:39:43 InnoDB: Compressed tables use zlib 1.2.7
 
230927 11:39:43 InnoDB: Using Linux native AIO
 
230927 11:39:43 InnoDB: Initializing buffer pool, size = 128.0M
 
230927 11:39:43 InnoDB: Completed initialization of buffer pool
 
230927 11:39:43 InnoDB: highest supported file format is Barracuda.
 
230927 11:39:43  InnoDB: Starting crash recovery from checkpoint LSN=248225431207
 
InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
 
230927 11:39:43  InnoDB: Assertion failure in thread 139734385055872 in file fsp0fsp.c line 2877
 
InnoDB: Failing assertion: space != 0

The assertion fails in the function fsp_reserve_free_pages(), which is not supposed to be called on the system tablespace (space=0).

Comment by Marko Mäkelä [ 2023-09-27 ]

Starting with MariaDB Server 10.6.9, thanks to MDEV-13542, the server should not crash in this case, but return an error to the operation that would have attempted to allocate a page within the system tablespace.

Please provide a fully resolved stack trace of the crash, so that this can be diagnosed.

Note that MariaDB 5.5 reached its end of life a few years ago.

Generated at Thu Feb 08 10:30:05 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.