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

Database crashes on startup InnoDB: Assertion failure in file ./storage/innobase/btr/btr0cur.cc line 297

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Affects Version/s: 10.6.5, 10.7.1
    • Fix Version/s: None
    • Labels:
    • Environment:
      Linux 5.15.6 on a BTRFS filesystem

      Description

      2022-01-09  9:46:34 0 [Note] /usr/sbin/mariadbd (server 10.6.5-MariaDB-1:10.6.5+maria~bullseye-log) starting as process 1834 ...
      2022-01-09  9:46:34 0 [Warning] You need to use --log-bin to make --binlog-format work.
      2022-01-09  9:46:34 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2022-01-09  9:46:34 0 [Note] InnoDB: Number of pools: 1
      2022-01-09  9:46:34 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
      2022-01-09  9:46:34 0 [Note] InnoDB: Using liburing
      2022-01-09  9:46:34 0 [Note] InnoDB: Initializing buffer pool, total size = 20401094656, chunk size = 134217728
      2022-01-09  9:46:34 0 [Note] InnoDB: Completed initialization of buffer pool
      2022-01-09  9:46:34 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=27704733209067,27704733209067
      2022-01-09  9:46:35 0 [Note] InnoDB: 19 transaction(s) which must be rolled back or cleaned up in total 27751 row operations to undo
      2022-01-09  9:46:35 0 [Note] InnoDB: Trx id counter is 113422811288
      2022-01-09  9:46:35 0 [Note] InnoDB: Starting final batch to recover 14 pages from redo log.
      2022-01-09  9:46:35 0 [Note] InnoDB: Last binlog file '/var/log/mysql/mysql-bin.000314', position 5935572
      2022-01-09  9:46:35 0 [Note] InnoDB: 128 rollback segments are active.
      2022-01-09  9:46:35 0 [Note] InnoDB: Starting in background the rollback of recovered transactions
      2022-01-09  9:46:35 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
      2022-01-09  9:46:35 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2022-01-09  9:46:35 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2022-01-09  9:46:35 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2022-01-09  9:46:35 0 [Note] InnoDB: 10.6.5 started; log sequence number 27704733225827; transaction id 113422811289
      2022-01-09  9:46:35 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      2022-01-09  9:46:35 0 [Note] Plugin 'FEEDBACK' is disabled.
      2022-01-09  9:46:35 0 [Warning] 'innodb-buffer-pool-instances' was removed. It does nothing now and exists only for compatibility with old my.cnf files.
      2022-01-09  9:46:35 0 [Warning] 'innodb-log-files-in-group' was removed. It does nothing now and exists only for compatibility with old my.cnf files.
      2022-01-09  9:46:35 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
      2022-01-09  9:46:35 0 [Note] Server socket created on IP: '0.0.0.0'.
      2022-01-09  9:46:35 0 [Note] /usr/sbin/mariadbd: ready for connections.
      Version: '10.6.5-MariaDB-1:10.6.5+maria~bullseye-log'  socket: '/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
      2022-01-09 09:46:35 0x7f60f12f8700  InnoDB: Assertion failure in file ./storage/innobase/btr/btr0cur.cc line 297
      InnoDB: Failing assertion: btr_page_get_next(latch_leaves.blocks[0]->frame) == block->page.id().page_no()
      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.
      220109  9:46:35 [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.6.5-MariaDB-1:10.6.5+maria~bullseye-log
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=0
      max_threads=3074
      thread_count=0
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6900114 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0
      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 = 0x0 thread_stack 0x49000
      ??:0(my_print_stacktrace)[0x559e1209c29e]
      ??:0(handle_fatal_signal)[0x559e11b61bd5]
      ??:0(__restore_rt)[0x7f65dd388140]
      ??:0(gsignal)[0x7f65dced1ce1]
      ??:0(abort)[0x7f65dcebb537]
      ??:0(Wsrep_server_service::log_dummy_write_set(wsrep::client_state&, wsrep::ws_meta const&))[0x559e11802bc7]
      ??:0(Wsrep_server_service::log_dummy_write_set(wsrep::client_state&, wsrep::ws_meta const&))[0x559e11805f5e]
      ??:0(void std::this_thread::sleep_for<long, std::ratio<1l, 1l> >(std::chrono::duration<long, std::ratio<1l, 1l> > const&))[0x559e11f7eca9]
      ??:0(void std::this_thread::sleep_for<long, std::ratio<1l, 1l> >(std::chrono::duration<long, std::ratio<1l, 1l> > const&))[0x559e11f0de93]
      ??:0(void std::this_thread::sleep_for<long, std::ratio<1l, 1l> >(std::chrono::duration<long, std::ratio<1l, 1l> > const&))[0x559e11f0def8]
      ??: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&&))[0x559e1202442d]
      ??: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&&))[0x559e120249ac]
      ??:0(void std::this_thread::sleep_for<long, std::ratio<1l, 1l> >(std::chrono::duration<long, std::ratio<1l, 1l> > const&))[0x559e11f1969b]
      ??:0(void std::this_thread::sleep_for<long, std::ratio<1l, 1l> >(std::chrono::duration<long, std::ratio<1l, 1l> > const&))[0x559e11ed128f]
      ??:0(void std::this_thread::sleep_for<long, std::ratio<1l, 1l> >(std::chrono::duration<long, std::ratio<1l, 1l> > const&))[0x559e11f3dbe8]
      ??:0(void std::this_thread::sleep_for<long, std::ratio<1l, 1l> >(std::chrono::duration<long, std::ratio<1l, 1l> > const&))[0x559e11f3efa8]
      ??:0(Wsrep_server_service::log_dummy_write_set(wsrep::client_state&, wsrep::ws_meta const&))[0x559e118008db]
      ??:0(tpool::task_group::execute(tpool::task*))[0x559e120349c9]
      ??:0(tpool::thread_pool_generic::worker_main(tpool::worker_data*))[0x559e12033c1f]
      ??:0(std::error_code::default_error_condition() const)[0x7f65dd26fed0]
      ??:0(start_thread)[0x7f65dd37cea7]
      ??:0(clone)[0x7f65dcf93def]
      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.
      Writing a core file...
      Working directory at /var/lib/mysql
      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             128343               128343               processes 
      Max open files            35111                35111                files     
      Max locked memory         65536                65536                bytes     
      Max address space         unlimited            unlimited            bytes     
      Max file locks            unlimited            unlimited            locks     
      Max pending signals       128343               128343               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: core
       
      Aborted
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              BuGless Stephen R. van den Berg
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:

                  Git Integration

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