InnoDB: Assertion failure in file storage/innobase/fsp/fsp0fsp.cc line 1562

2022-07-19 07:34:48 0x7fe2fa7fc700  InnoDB: Assertion failure in file /home/abuild/rpmbuild/BUILD/mariadb-10.5.16/storage/innobase/fsp/fsp0fsp.cc line 1562

InnoDB: Failing assertion: inode

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 mysqld 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.

220719  7:34:48 [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: 10.5.16-MariaDB-log

key_buffer_size=16384

read_buffer_size=131072

max_used_connections=32

max_threads=258

thread_count=33

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 567973 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x558db7e11948

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 = 0x7fe2fa7fbb88 thread_stack 0x49000

??:0(my_print_stacktrace)[0x558db58ca73d]

??:0(handle_fatal_signal)[0x558db5342495]

??:0(__restore_rt)[0x7fe34d4168c0]

??:0(__GI_raise)[0x7fe34be4acdb]

??:0(__GI_abort)[0x7fe34be4c375]

/usr/sbin/mysqld(+0x6464d8)[0x558db50464d8]

??:0(void std::vector<unsigned long, std::allocator<unsigned long> >::_M_realloc_insert<unsigned long>(__gnu_cxx::__normal_iterator<unsigned long*, std::vector<unsigned long, std::allocator<unsigned long> > >, unsigned long&&))[0x558db58063ec]

??:0(void std::vector<unsigned long, std::allocator<unsigned long> >::_M_realloc_insert<unsigned long>(__gnu_cxx::__normal_iterator<unsigned long*, std::vector<unsigned long, std::allocator<unsigned long> > >, unsigned long&&))[0x558db580a495]

??:0(std::_Rb_tree<unsigned int, unsigned int, std::_Identity<unsigned int>, std::less<unsigned int>, std::allocator<unsigned int> >::_M_erase(std::_Rb_tree_node<unsigned int>*))[0x558db5724097]

??:0(std::_Rb_tree<unsigned int, unsigned int, std::_Identity<unsigned int>, std::less<unsigned int>, std::allocator<unsigned int> >::_M_erase(std::_Rb_tree_node<unsigned int>*))[0x558db5727c28]

??:0(std::unique_lock<std::mutex>::unlock())[0x558db570b173]

??:0(tpool::task_group::execute(tpool::task*))[0x558db586a131]

??:0(tpool::thread_pool_generic::worker_main(tpool::worker_data*))[0x558db5868eff]

??:0(std::error_code::default_error_condition() const)[0x7fe34cadb3d4]

??:0(start_thread)[0x7fe34d40a6ea]

??:0(__GI___clone)[0x7fe34bf17a8f]

Trying to get some variables.

Some pointers may be invalid and cause the dump to abort.

Query (0x0): (null)

Connection ID (thread ID): 0

Status: NOT_KILLED

Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on,not_null_range_scan=off

The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains

information that should help you find out what is causing the crash.

We think the query pointer is invalid, but we will try to print it anyway. 

Query: 

Writing a core file...

Working directory at /home/eike/.local/share/akonadi/db_data

Resource Limits:

Limit                     Soft Limit           Hard Limit           Units     

Max cpu time              unlimited            unlimited            seconds   

Max file size             unlimited            unlimited            bytes     

Max data size             unlimited            unlimited            bytes     

Max stack size            8388608              unlimited            bytes     

Max core file size        unlimited            unlimited            bytes     

Max resident set          unlimited            unlimited            bytes     

Max processes             125993               125993               processes 

Max open files            8192                 524288               files     

Max locked memory         8388608              8388608              bytes     

Max address space         unlimited            unlimited            bytes     

Max file locks            unlimited            unlimited            locks     

Max pending signals       125993               125993               signals   

Max msgqueue size         819200               819200               bytes     

Max nice priority         0                    0                    

Max realtime priority     0                    0                    

Max realtime timeout      unlimited            unlimited            us        

Core pattern: |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h