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

MariaDB 5.5 fails to start with 10.0 InnoDB log files

Details

    Description

      When default log file size is used database created using 10.0 fails to start using 5.5 on following message:

      nnoDB: Error: log file ./ib_logfile0 is of different size 0 50331648 bytes
      InnoDB: than specified in the .cnf file 0 5242880 bytes!
      140521 12:24:53 [ERROR] Plugin 'InnoDB' init function returned error.
      140521 12:24:53 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
      140521 12:24:53 [ERROR] Unknown/unsupported storage engine: InnoDB
      140521 12:24:53 [ERROR] Aborting

      This is because in 10.0 by default log file size is 48M when 5.5 it is 5M.

      Attachments

        Activity

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

          ------------------------------------------------------------
          revno: 4191
          committer: Jan Lindström <jplindst@mariadb.org>
          branch nick: 5.5
          timestamp: Wed 2014-05-21 13:14:43 +0300
          message:
          MDEV-6257: MariaDB 5.5 fails to start with 10.0 InnoDB log files

          Analysis: By default 10.0 creates 48M log files and 5.5 assumes they
          are 5M.

          Fix: Remove the error and do size comparison later.

          jplindst Jan Lindström (Inactive) added a comment - ------------------------------------------------------------ revno: 4191 committer: Jan Lindström <jplindst@mariadb.org> branch nick: 5.5 timestamp: Wed 2014-05-21 13:14:43 +0300 message: MDEV-6257 : MariaDB 5.5 fails to start with 10.0 InnoDB log files Analysis: By default 10.0 creates 48M log files and 5.5 assumes they are 5M. Fix: Remove the error and do size comparison later.
          nirbhay_c Nirbhay Choubey (Inactive) added a comment -

          Same happens on trying to start mysql-5.5 with mysql-5.6 innodb log files.

          nirbhay_c Nirbhay Choubey (Inactive) added a comment - Same happens on trying to start mysql-5.5 with mysql-5.6 innodb log files.
          jplindst Jan Lindström (Inactive) added a comment -

          This fix should solve that also, but not tested.

          jplindst Jan Lindström (Inactive) added a comment - This fix should solve that also, but not tested.
          axel Axel Schwenke added a comment -

          The default log size has changed from 5.5 to 10.0. It's just one of several incompatible changes. The workaround is easy - put the log file size into my.cnf.

          I think the bug bad behavior is, that with no log size set in my.cnf, InnoDB forces a default size. Instead it should just look at the existing logs to find out which size they are. I don't think this is a genuine bug but rather a feature request.

          axel Axel Schwenke added a comment - The default log size has changed from 5.5 to 10.0. It's just one of several incompatible changes. The workaround is easy - put the log file size into my.cnf. I think the bug bad behavior is, that with no log size set in my.cnf, InnoDB forces a default size. Instead it should just look at the existing logs to find out which size they are. I don't think this is a genuine bug but rather a feature request.
          jplindst Jan Lindström (Inactive) added a comment -

          You now may open log files with different innodb_log_file_size setup. This seems not be protected. Lets get back to drawing board.

          jplindst Jan Lindström (Inactive) added a comment - You now may open log files with different innodb_log_file_size setup. This seems not be protected. Lets get back to drawing board.
          jplindst Jan Lindström (Inactive) added a comment -

          revno: 4192
          committer: Jan Lindström <jplindst@mariadb.org>
          branch nick: 5.5
          timestamp: Thu 2014-05-22 16:20:56 +0300
          message:
          MDEV-6257: MariaDB 5.5 fails to start with 10.0 InnoDB log files

          Analysis: Can't disable the error message because you may get database
          started with incorrect log file size.

          Fix: Thus only improve the error message to give more information
          to users.

          jplindst Jan Lindström (Inactive) added a comment - revno: 4192 committer: Jan Lindström <jplindst@mariadb.org> branch nick: 5.5 timestamp: Thu 2014-05-22 16:20:56 +0300 message: MDEV-6257 : MariaDB 5.5 fails to start with 10.0 InnoDB log files Analysis: Can't disable the error message because you may get database started with incorrect log file size. Fix: Thus only improve the error message to give more information to users.
          nirbhay_c Nirbhay Choubey (Inactive) added a comment -

          As Axel suggested, can't we make server/innodb to derive the log file size and use it, instead of just aborting?

          nirbhay_c Nirbhay Choubey (Inactive) added a comment - As Axel suggested, can't we make server/innodb to derive the log file size and use it, instead of just aborting?
          danblack Daniel Black added a comment -

          And/or if its a clean startup move the 5M ones out of the way and create them.

          innodb_log_files_in_group could be derived too.

          danblack Daniel Black added a comment - And/or if its a clean startup move the 5M ones out of the way and create them. innodb_log_files_in_group could be derived too.

          People

            jplindst Jan Lindström (Inactive)
            jplindst Jan Lindström (Inactive)
            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.