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

Page 38:4016 may be corrupted. Post encryption checksum 3690179534 stored

    XMLWordPrintable

Details

    Description

      hi

      In a Mariadb replication setup (1 master, 1 slave)

      We got an
      InnoDB: Page 38:4016 may be corrupted. Post encryption checksum 3690179534 stored [3690179534:3690179534] key_version

      for no obvious reason, no HW failure or anything noticeable at OS level.

      Then a bit later : Got error 192 when reading table

      We had to switch role to let the application operate again. That went OK, although we lost the rows that could not be replicated for the corrupted table.

      After a while, the old master that was promoted to slaved crashed an could not be restarted, besides using recovery level 6.

      We ended resyncing with full backup but the issue is scary.

      Asking for analysis and feedback.

      Thank you
      Emmanuel

      Attachments

        1. before_innocrash_20191105.txt
          10 kB
          Emmanuel Torre
        2. innocrash_20191105.txt
          26 kB
          Emmanuel Torre

        Issue Links

          Activity

            People

              Unassigned Unassigned
              etorre Emmanuel Torre
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.