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

InnoDB: Assertion failure

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Cannot Reproduce
    • 10.3.32, 10.3.33, 10.3.34
    • N/A
    • Storage Engine - InnoDB
    • Product version: Plesk Obsidian 18.0.42.1
      OS version: CloudLinux 7.9 x86_64
      Build date: 2022/03/14 17:00

    Description

      Version 10.3.32
      2022-02-12 21:27:54 0x7ff3d8956700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.32/storage/innobase/btr/btr0cur.cc line 7699

      Version 10.3.33
      2022-03-18 00:04:16 0x7fca28acc700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.33/storage/innobase/btr/btr0cur.cc line 7699

      Version 10.3.34 (Error still there):
      2022-03-24 17:08:49 0x7fed3c4ae700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.34/storage/innobase/btr/btr0cur.cc line 7699

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13542 Crashing on a corrupted page is unhelpful

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            marko Marko Mäkelä added a comment -

            The failing assertion is a consistency check in btr_check_blob_fil_page_type():

                    ut_a(space_id == page_get_space_id(page));

            It suggests that a BLOB pointer in a clustered index record is pointing to an invalid page. There are various possible reasons for that, such as, an attempt to "fix" crash recovery failures by removing ib_logfile*, or an attempt to copy data files while the server is running, without using a tool like mariabackup.

            I am not aware of any currently open BLOB bugs.

            marko Marko Mäkelä added a comment - The failing assertion is a consistency check in btr_check_blob_fil_page_type() : ut_a(space_id == page_get_space_id(page)); It suggests that a BLOB pointer in a clustered index record is pointing to an invalid page. There are various possible reasons for that, such as, an attempt to "fix" crash recovery failures by removing ib_logfile* , or an attempt to copy data files while the server is running, without using a tool like mariabackup . I am not aware of any currently open BLOB bugs.
            marko Marko Mäkelä added a comment -

            Can you reproduce this bug after initializing a new database from an SQL dump?

            marko Marko Mäkelä added a comment - Can you reproduce this bug after initializing a new database from an SQL dump?
            mosmani Muhamed Osmani added a comment -

            After initiaziling and recover from a dump the error dissappeared...

            mosmani Muhamed Osmani added a comment - After initiaziling and recover from a dump the error dissappeared...

            People

              marko Marko Mäkelä
              mosmani Muhamed Osmani
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.