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

innodb_force_recovery = 6 cannot recover ANY DATA when change buffer not empty

Details

    • 10.1.11, 10.1.14

    Description

      Innodb force recovery settings prevent its own recovery. In innodb_force_recovery=6 and read only mode, no reason to expect change or doublewrite buffers to be empty. It does however complain about the change buffer not being empty:

      [ERROR] InnoDB: Change buffer must be empty when --innodb-read-only is set!

      Same bug in MySQL:
      https://bugs.mysql.com/bug.php?id=77476

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-8963 innodb_force_recovery >= 4 won't work

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          links to

          Web Link Bug #77476 innodb_force_recovery = 6 cannot recover ANY DATA when change buffer not empty

          Activity

            Ascending order - Click to sort in descending order
            jplindst Jan Lindström (Inactive) added a comment -

            Could this be because of MDEV-8963, but that should be fixed on innodb_plugin and MySQL 5.6.27 and MariaDB 10.1.9 (to be released) ?

            jplindst Jan Lindström (Inactive) added a comment - Could this be because of MDEV-8963 , but that should be fixed on innodb_plugin and MySQL 5.6.27 and MariaDB 10.1.9 (to be released) ?
            jplindst Jan Lindström (Inactive) added a comment -

            commit 071ae303bd7ad6ce71f05a25695cd0e9fcef112c
            Author: Jan Lindström <jan.lindstrom@mariadb.com>
            Date: Wed Apr 27 11:07:43 2016 +0300

            MDEV-9121: innodb_force_recovery = 6 cannot recover ANY DATA when
            change buffer not empty

            Fix: Allow not empty change buffer when innodb_force_recovery >= 5
            and output only a warning to error log.

            Note: Before using force recovery you should always take backup
            of your database.

            jplindst Jan Lindström (Inactive) added a comment - commit 071ae303bd7ad6ce71f05a25695cd0e9fcef112c Author: Jan Lindström <jan.lindstrom@mariadb.com> Date: Wed Apr 27 11:07:43 2016 +0300 MDEV-9121 : innodb_force_recovery = 6 cannot recover ANY DATA when change buffer not empty Fix: Allow not empty change buffer when innodb_force_recovery >= 5 and output only a warning to error log. Note: Before using force recovery you should always take backup of your database.

            People

              jplindst Jan Lindström (Inactive)
              dignus81 Johan Kooijman
              Votes:
              3 Vote for this issue
              Watchers:
              5 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.