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

InnoDB: Failing assertion: pcur->restore_position(BTR_MODIFY_TREE, mtr) == btr_pcur_t::SAME_ALL



    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.6.12, 11.2.0
    • 11.2
    • None
    • MariaDB 10.6.12 running on AWS RDS r6g class.


      Recently upgraded our DB replica server from MariaDB 10.4.22 to 10.6.12. Upgraded a few other prior with no issues. Ran into an assertion error that crashed only on one of our replicas (oddly enough, the others were fine). Stack trace shows an UPDATE statement caused the crash.

      ```0x40003629b8f0 InnoDB: Assertion failure in file /local/p4clients/pkgbuild-_nuWH/workspace/src/RDSMariaDB/storage/innobase/row/row0upd.cc line 2413
      InnoDB: Failing assertion: pcur->restore_position(BTR_MODIFY_TREE, mtr) == btr_pcur_t::SAME_ALL
      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.
      230302 17:28:39 [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.12-MariaDB-log source revision:
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 27964704 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x4060c3208d18
      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 = 0x40003629b060 thread_stack 0x40000
      Printing to addr2line failed

      After digging around, this looks like an old bug that was fixed - https://bugs.mysql.com/bug.php?id=53390. Verified there are no BLOB columns being used either.


        Issue Links



              marko Marko Mäkelä
              inderjitbassi Inderjit Bassi
              0 Vote for this issue
              3 Start watching this issue



                Git Integration

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