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

Mariadb crash after upgrading to 11.0.3: Failing assertion: local_len >= BTR_EXTERN_FIELD_REF_SIZE

    XMLWordPrintable

Details

    Description

      After hitting this issue https://jira.mariadb.org/browse/MDEV-31579 and waiting for a fix in 11.0.3, I thought we were in the clear.

      However, a couple of minutes into running 11.0.3, the server crashed, and now keeps crashing every few minutes.

      2023-08-30 14:09:49 0x7fadf061e700  InnoDB: Assertion failure in file /home/abuild/rpmbuild/BUILD/mariadb-11.0.3/storage/innobase/btr/btr0cur.cc line 6702
      InnoDB: Failing assertion: local_len >= BTR_EXTERN_FIELD_REF_SIZE
      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.
      230830 14:09:49 [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: 11.0.3-MariaDB-log source revision: 70905bcb9059dcc40db3b73bc46a36c7d40f1e10
      key_buffer_size=536870912
      read_buffer_size=262144
      max_used_connections=24
      max_threads=2050
      thread_count=22
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 5301930 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7fad3c000c58
      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 = 0x7fadf061dd08 thread_stack 0x49000
      /usr/sbin/mysqld(my_print_stacktrace+0x3d)[0x55ea4835712d]
      /usr/sbin/mysqld(handle_fatal_signal+0x575)[0x55ea47e60215]
      corrupted size vs. prev_size
      

      Any idea what this crash is about?

      Attachments

        1. screenshot-1.png
          screenshot-1.png
          86 kB
        2. page.bin
          16 kB
        3. image-2023-09-07-12-33-35-832.png
          image-2023-09-07-12-33-35-832.png
          2 kB
        4. ibuf_page.bin.xz
          0.1 kB

        Issue Links

          Activity

            People

              marko Marko Mäkelä
              archon810 Artem Russakovskii
              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.