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

Still getting assertion failure in file data0type.cc line 67

Details

    Description

      This error is essentially the same as MDEV-20726, except that is still happens for me. I'm running mariadb server version 10.4.13-MariaDB-1:10.4.13+maria~bionic.

      Here is a very short example which reproduces the error (Careful - crashes the server and prevents it from restarting!)

      CREATE TABLE `Foo`
      		 
      (
      		 
          `Bar` char(2) CHARACTER SET utf8,
      		 
          KEY `Bar` (`Bar`(1))
      		 
      ) ENGINE = InnoDB;
      		 
       
      		 
      ALTER TABLE `Foo` MODIFY `Bar` char(2) CHARACTER SET utf8mb4;
      		 
       
      		 
      INSERT INTO Foo VALUES ('a');

      At this point the server crashes and cannot restart, always crashing again with the error message "InnoDB: Failing assertion: !(prefix_len % mbmaxlen)".

      Observations: The error only occurs if the index is a prefix index. It also doesn't occur if the collation is changed in the ALTER TABLE - going from utf8_bin to utf8mb4_bin triggers the bug, as does going from utf8_general_ci to utf8mb4_general_ci, but when going from utf8_general_ci to utf8mb4_bin it does not occur.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-22898 SQL query always crashes on INSERT IGNORE

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-24419 Galera crash after ALTER TABLE convert to utf8mb4: Assertion failure in file data0type.cc line 67

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-20726 InnoDB: Assertion failure in file data0type.cc line 67

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-23964 MariaDB 10.5.4 and 10.5.6 replica keeps crashing when the a 10.2.x master run a `ALTER TABLE CHARACTER utf8mb4`

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            medo Simeon Maxein created issue -
            medo Simeon Maxein made changes -
            Field Original Value New Value
            marko Marko Mäkelä made changes -
            Fix Version/s 10.4 [ 22408 ]
            Fix Version/s 10.5 [ 23123 ]
            Assignee Marko Mäkelä [ marko ]
            marko Marko Mäkelä made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            marko Marko Mäkelä made changes -
            Assignee Marko Mäkelä [ marko ] Eugene Kosov [ kevg ]
            elenst Elena Stepanova made changes -
            kevg Eugene Kosov (Inactive) made changes -
            kevg Eugene Kosov (Inactive) made changes -
            kevg Eugene Kosov (Inactive) made changes -
            Fix Version/s 10.4.14 [ 24305 ]
            Fix Version/s 10.5.5 [ 24423 ]
            Fix Version/s 10.4 [ 22408 ]
            Fix Version/s 10.5 [ 23123 ]
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Closed [ 6 ]
            alice Alice Sherepa made changes -
            marko Marko Mäkelä made changes -
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 111475 ] MariaDB v4 [ 158127 ]

            People

              kevg Eugene Kosov (Inactive)
              medo Simeon Maxein
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.