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

Assertion `purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no()'

    XMLWordPrintable

Details

    Description

      The process exits during mysqld execution, and an error occurs after restarting.

      lead to:

      InnoDB: Failing assertion: purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no()
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      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: https://mariadb.com/kb/en/library/innodb-recovery-modes/
      InnoDB: about forcing recovery.
      220914 18:23:30 [ERROR] mysqld got signal 6 ;
      

      Attachments

        1. data.tar.xz
          927 kB
          Marko Mäkelä

        Issue Links

          Activity

            People

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