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

Innodb reports Assertion failure in file buf0dblwr.cc line 579

    XMLWordPrintable

    Details

    • Sprint:
      10.1.14

      Description

      I have installed mariadb 10.1.9 in virtualbox with some tables compressed using "ENGINE=Innodb,COLLATE=utf8mb4_bin,page_compressed=1;" in create statements.
      After I power off the machine when mariadb is running,of course its data is corrupted.But what is important is that it reports the following assertion failure during recovery:

      2015-12-07 09:33:52 7f6ecb1f1760  InnoDB: Assertion failure in thread 140113830942560 in file buf0dblwr.cc line 579 
      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.
      151207  9:33:52 [ERROR] mysqld got signal 6 ; 
      This could be because you hit a bug. It is also possible that this binary
      or one of the libraries it was linked against is corrupt, improperly built,
      or misconfigured. This error can also be caused by malfunctioning hardware

      Can mariadb automatically recover data in such situations?
      PS:The full error log is in the attachment.

        Attachments

          Activity

            People

            Assignee:
            jplindst Jan Lindström
            Reporter:
            cyy chen yuanyuan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: