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

Upgrade from 10.7 or earlier may crash if innodb_log_file_buffering=OFF

Details

    Description

      Upgrading from Debian 11 to Debian 12 yields an exception from which mariadb doesn't seem to recover from. This can reproduced with a clean installation and no data inserted whatsoever. It seems as if it has to do something with the InnoDB structure that was generated with version 10.5.19. I tested this with both Debian 11 (5.10.0.-23) and Debian 12 (6.1.0-9) kernels with both failing.

      The only fix for this seems to be to delete /var/lib/mysql in its entirety and regenerate all of the data structures by starting up mariadb with an empty dir. From this point on the exception is gone and everything works as expected.

      I attached the error log that comes up when /usr/sbin/mariadbd is started with version 10.11.3 with data generated from 10.5.19.

      Attachments

        Issue Links

          Activity

            leo_ Leonardo Martinho created issue -
            marko Marko Mäkelä made changes -
            Field Original Value New Value
            marko Marko Mäkelä made changes -
            Component/s Storage Engine - InnoDB [ 10129 ]
            leo_ Leonardo Martinho made changes -
            Attachment mariadbd_strace [ 70876 ]
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            Fix Version/s 10.9 [ 26905 ]
            Fix Version/s 10.10 [ 27530 ]
            Fix Version/s 10.11 [ 27614 ]
            Fix Version/s 11.0 [ 28320 ]
            Fix Version/s 11.1 [ 28549 ]
            Fix Version/s 11.2 [ 28603 ]
            Affects Version/s 10.8 [ 26121 ]
            Affects Version/s 10.9 [ 26905 ]
            Affects Version/s 10.10 [ 27530 ]
            Affects Version/s 10.11 [ 27614 ]
            Affects Version/s 11.0 [ 28320 ]
            Affects Version/s 11.1 [ 28549 ]
            Affects Version/s 11.2 [ 28603 ]
            Assignee Marko Mäkelä [ marko ]
            Labels crash upgrade
            Priority Major [ 3 ] Critical [ 2 ]
            Summary Upgrade from mariadb server 10.5.19 to mariadb server 10.11.3 yields exception on s390x arch Upgrade from 10.7 or earlier may crash if innodb_log_file_buffering=OFF
            marko Marko Mäkelä made changes -
            Status Open [ 1 ] Confirmed [ 10101 ]
            marko Marko Mäkelä made changes -
            issue.field.resolutiondate 2023-07-10 08:58:28.0 2023-07-10 08:58:28.714
            marko Marko Mäkelä made changes -
            Fix Version/s 10.9.8 [ 29015 ]
            Fix Version/s 10.10.6 [ 29017 ]
            Fix Version/s 10.11.5 [ 29019 ]
            Fix Version/s 11.0.3 [ 28920 ]
            Fix Version/s 11.1.2 [ 28921 ]
            Fix Version/s 11.2.1 [ 29034 ]
            Fix Version/s 10.9 [ 26905 ]
            Fix Version/s 10.10 [ 27530 ]
            Fix Version/s 10.11 [ 27614 ]
            Fix Version/s 11.0 [ 28320 ]
            Fix Version/s 11.1 [ 28549 ]
            Fix Version/s 11.2 [ 28603 ]
            Resolution Fixed [ 1 ]
            Status Confirmed [ 10101 ] Closed [ 6 ]
            danblack Daniel Black made changes -

            People

              marko Marko Mäkelä
              leo_ Leonardo Martinho
              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.