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

innodb_force_recovery >= 4 won't work

    XMLWordPrintable

Details

    • 10.1.9-1, 10.1.9-2

    Description

      This bug has been reported here https://bugs.mysql.com/bug.php?id=77654.

      My InnoDB got corrupted and mariadb crashes every time i start it, so i tried using innodb_force_recovery option, values 1-3 still crash and >=4 InnoDB refuses to work:

      2015-10-18 20:27:43 3068483456 [Warning] InnoDB: Recovery skipped, --innodb-read-only set!
      2015-10-18 20:27:43 3068483456 [Note] InnoDB: The log sequence numbers 420559692 and 420559692 in ibdata files do not match the log sequence number 21215150453 in the ib_logfiles!
      2015-10-18 20:27:43 3068483456 [ERROR] InnoDB: Can't initiate database recovery, running in read-only-mode.
      2015-10-18 20:27:43 3068483456 [ERROR] Plugin 'InnoDB' init function returned error.
      2015-10-18 20:27:43 3068483456 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
      2015-10-18 20:27:43 3068483456 [Note] Plugin 'FEEDBACK' is disabled.
      2015-10-18 20:27:43 3068483456 [ERROR] Unknown/unsupported storage engine: InnoDB
      2015-10-18 20:27:43 3068483456 [ERROR] Aborting

      Attachments

        Issue Links

          Activity

            People

              jplindst Jan Lindström (Inactive)
              nnnn20430 20430
              Votes:
              0 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.