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

InnoDB should refuse to start if crash recovery fails instead of asserting

Details

    • 10.1.8-3

    Description

      2015-09-16 15:21:28 7fd806d4e780  InnoDB: Operating system error number 2 in a file operation.
      InnoDB: The error means the system cannot find the path specified.
      InnoDB: If you are installing InnoDB, remember that you must create
      InnoDB: directories yourself, InnoDB does not create them.
      InnoDB: Error: could not open single-table tablespace file ./test/#sql-5a51_9#P#p0.ibd
      2015-09-16 15:21:28 140565804279680 [Note] InnoDB: Restoring possible half-written data pages 
      2015-09-16 15:21:28 140565804279680 [Note] InnoDB: from the doublewrite buffer...
      InnoDB: Set innodb_force_recovery to ignore this error.
      2015-09-16 15:21:28 7fd806d4e780  InnoDB: Assertion failure in thread 140565804279680 in file log0recv.cc line 2776
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
      InnoDB: If you get repeated assertion failures or crashes, even
      InnoDB: immediately after the mysqld startup, there may be
      InnoDB: corruption in the InnoDB tablespace. Please refer to
      InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
      InnoDB: about forcing recovery.
      150916 15:21:28 [ERROR] mysqld got signal 6 ;

      Attachments

        Activity

          jplindst Jan Lindström (Inactive) created issue -
          ratzpo Rasmus Johansson (Inactive) made changes -
          Field Original Value New Value
          Sprint 10.1.8-3 [ 15 ]
          ratzpo Rasmus Johansson (Inactive) made changes -
          Rank Ranked higher
          jplindst Jan Lindström (Inactive) made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          jplindst Jan Lindström (Inactive) made changes -
          Summary InnoDB should refuse to start if tablespace is not found instead of asserting InnoDB should refuse to start if crash recovery fails instead of asserting
          jplindst Jan Lindström (Inactive) made changes -
          Fix Version/s 10.1.8 [ 19605 ]
          Fix Version/s 10.1 [ 16100 ]
          Resolution Fixed [ 1 ]
          Status In Progress [ 3 ] Closed [ 6 ]
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 71652 ] MariaDB v4 [ 149621 ]

          People

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