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

Failing assertion: !i || prev_id + 1 == space_id

    XMLWordPrintable

Details

    Description

      2023-06-20 13:03:07 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2023-06-20 13:03:07 0 [Note] InnoDB: Number of transaction pools: 1
      2023-06-20 13:03:07 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
      2023-06-20 13:03:07 0 [Note] InnoDB: Initializing buffer pool, total size = 200.000GiB, chunk size = 3.125GiB
      2023-06-20 13:03:08 0 [Note] InnoDB: Completed initialization of buffer pool
      2023-06-20 13:03:08 0 [ERROR] InnoDB: Inconsistent tablespace ID in file /db/main/InnoUndo/undo001
      2023-06-20 13:03:08 0 [ERROR] InnoDB: Unable to read first page of file /db/main/InnoUndo/undo001
      2023-06-20 13:03:08 0 [ERROR] InnoDB: Inconsistent tablespace ID in file /db/main/InnoUndo/undo002
      2023-06-20 13:03:08 0 [ERROR] InnoDB: Unable to read first page of file /db/main/InnoUndo/undo002
      2023-06-20 13:03:08 0x7f9257d60840 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.11.4/storage/innobase/srv/srv0start.cc
      line 804
      InnoDB: Failing assertion: !i || prev_id + 1 == space_id
      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.
      230620 13:03:08 [ERROR] mysqld got signal 6 ;

      Server version: 10.11.4-MariaDB-1:10.11.4+maria~deb10-log source revision: 4e2b93dffef2414a11ca5edc8d215f57ee5010e5
      key_buffer_size=131072
      read_buffer_size=131072
      max_used_connections=0
      max_threads=5002
      thread_count=0
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 11016811 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
      /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x5649c7b1629e]
      /usr/sbin/mariadbd(handle_fatal_signal+0x485)[0x5649c760c035]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7f3dfd498730]
      /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b)[0x7f3dfcfef8eb]
      /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f3dfcfda535]
      /usr/sbin/mariadbd(+0x68976e)[0x5649c726376e]
      /usr/sbin/mariadbd(+0x681b50)[0x5649c725bb50]
      /usr/sbin/mariadbd(+0x683fdc)[0x5649c725dfdc]
      /usr/sbin/mariadbd(+0xce50f1)[0x5649c78bf0f1]
      /usr/sbin/mariadbd(_Z24ha_initialize_handlertonP13st_plugin_int+0x84)[0x5649c760f3f4]
      /usr/sbin/mariadbd(+0x81175b)[0x5649c73eb75b]
      /usr/sbin/mariadbd(_Z11plugin_initPiPPci+0xa2b)[0x5649c73eca3b]
      /usr/sbin/mariadbd(+0x70037f)[0x5649c72da37f]
      /usr/sbin/mariadbd(_Z11mysqld_mainiPPc+0x3d6)[0x5649c72df906]
      /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7f3dfcfdc09b]
      /usr/sbin/mariadbd(_start+0x2a)[0x5649c72d3faa]
      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 /db/main/tables
      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 1031221 1031221 processes
      Max open files 32768 32768 files
      Max locked memory 65536 65536 bytes
      Max address space unlimited unlimited bytes
      Max file locks unlimited unlimited locks
      Max pending signals 1031221 1031221 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

      Kernel version: Linux version 4.19.0-24-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.282-1 (2023-04-29)

      Attachments

        Issue Links

          Activity

            People

              marko Marko Mäkelä
              alexcool Alex
              Votes:
              1 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.