Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-36019

MariaDB crashes with "InnoDB: InnoDB is trying to free page [page id: space=0, page number=27212048] though it is already marked as free in the tablespace!"

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Not a Bug
    • 10.4.28
    • N/A
    • Server
    • Oracle Linux 8

    Description

      MariaDB crashed with the following:

      2025-01-31 19:26:15 1 [ERROR] [FATAL] InnoDB: InnoDB is trying to free page [page id: space=0, page number=27212048] though it is already marked as free in the tablespace! The tablespace free space info is corrupt. You may need to dump your tables and recreate the whole database!Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
      250131 19:26:15 [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.4.28-MariaDB-log source revision: c8f2e9a5c0ac5905f28b050b7df5a9ffd914b7e7
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=12
      max_threads=2002
      thread_count=17
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4537151 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7ecb64c060c8
      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 = 0x7ecb679f92a8 thread_stack 0x49000
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55c3e064637e]
      /usr/sbin/mysqld(handle_fatal_signal+0x55d)[0x55c3e00f4f3d]
      /lib64/libpthread.so.0(+0x12d00)[0x7fdbd59b7d00]
      /lib64/libc.so.6(gsignal+0x10f)[0x7fdbd4d13b8f]
      /lib64/libc.so.6(abort+0x127)[0x7fdbd4ce6ea5]
      /usr/sbin/mysqld(+0x5c7403)[0x55c3dfdfc403]
      /usr/sbin/mysqld(+0x5db496)[0x55c3dfe10496]
      /usr/sbin/mysqld(+0xd54cd1)[0x55c3e0589cd1]
      /usr/sbin/mysqld(+0xc81617)[0x55c3e04b6617]
      /usr/sbin/mysqld(+0xc841cc)[0x55c3e04b91cc]
      /usr/sbin/mysqld(+0xc705c2)[0x55c3e04a55c2]
      /lib64/libpthread.so.0(+0x81da)[0x7fdbd59ad1da]
      :0(__GI___clone)[0x7fdbd4cfee73]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x0): (null)
      Connection ID (thread ID): 1
      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
       
      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 /data.local/db
      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        0                    unlimited            bytes     
      Max resident set          unlimited            unlimited            bytes     
      Max processes             5644125              5644125              processes 
      Max open files            1048576              1048576              files     
      Max locked memory         65536                65536                bytes     
      Max address space         unlimited            unlimited            bytes     
      Max file locks            unlimited            unlimited            locks     
      Max pending signals       5644125              5644125              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 %e
       
      Kernel version: Linux version 4.18.0-425.19.2.0.1.el8_7.x86_64 (mockbuild@host-100-100-224-19) (gcc version 8.5.0 20210514 (Red Hat 8.5.0-16.0.2) (GCC)) #1 SMP Tue Apr 4 13:26:06 PDT 2023
      

      It starts up with innodb_force_recovery=2, but once restarted without the force recovery flag, it keeps crashing and restarting every 2 minutes.

      Attachments

        Activity

          People

            marko Marko Mäkelä
            ltsoi@sciencelogic.com Leonid Tsoi
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.