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

On upgrade, InnoDB reports "started; log sequence number 0"

    XMLWordPrintable

Details

    Description

      When InnoDB is upgrading the redo log from an earlier MariaDB or MySQL version, it outputs messages like this:

      2018-01-08  5:39:50 140390495905984 [Note] InnoDB: Upgrading redo log: 2*536870912 bytes; LSN=1395657325222
      2018-01-08  5:39:50 140390495905984 [Note] InnoDB: Starting to delete and rewrite log files.
      2018-01-08  5:39:50 140390495905984 [Note] InnoDB: Setting log file ./ib_logfile101 size to 536870912 bytes
      2018-01-08  5:39:50 140390495905984 [Note] InnoDB: Setting log file ./ib_logfile1 size to 536870912 bytes
      2018-01-08  5:39:50 140390495905984 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
      2018-01-08  5:39:50 140390495905984 [Note] InnoDB: New log files created, LSN=1395657325222
      2018-01-08  6:01:49 140390495905984 [Note] InnoDB: 128 out of 128 rollback segments are active.
      2018-01-08  6:01:49 140390495905984 [Note] InnoDB: Creating sys_virtual system tables.
      2018-01-08  6:01:49 140390495905984 [Note] InnoDB: Creating shared tablespace for temporary tables
      2018-01-08  6:01:49 140390495905984 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2018-01-08  6:01:49 140390495905984 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2018-01-08  6:01:49 140390495905984 [Note] InnoDB: Waiting for purge to start
      2018-01-08  6:01:49 140390495905984 [Note] InnoDB: 5.7.20 started; log sequence number 0
      

      The last message should report the same LSN as the earlier messages, instead of reporting 0.

      Attachments

        Activity

          People

            marko Marko Mäkelä
            marko Marko Mäkelä
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.