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

innodb.log_data_file_size failed in buildbot with InnoDB: Database page corruption

    XMLWordPrintable

Details

    Description

      http://buildbot.askmonty.org/buildbot/builders/winx64-debug/builds/3657/steps/test/logs/stdio

      innodb.innodb-alter-debug 'innodb_plugin' w2 [ pass ]    965
      innodb.log_data_file_size 'xtradb'       w1 [ fail ]  Found warnings/errors in server log file!
              Test ended at 2017-05-05 18:40:03
      line
      2017-05-05 18:40:00 5016 [Warning] InnoDB: A copy of page 4:4 in the doublewrite buffer slot 17 is not within space bounds
       
      2017-05-05 18:40:00 5016 [Warning] InnoDB: A copy of page 5:4 in the doublewrite buffer slot 23 is not within space bounds
       
      2017-05-05 18:40:00 5016 [Warning] InnoDB: A copy of page 6:5 in the doublewrite buffer slot 30 is not within space bounds
       
      2017-05-05 18:40:02 4704 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/ibd4f page  [page id: space=5, page number=4]. You may have to recover from a backup.
       
      2017-05-05 18:40:02 4704 [ERROR] InnoDB: Read operation failed for tablespace ./test/ibd4f.ibd offset 4 with error Page read from tablespace is corrupted.
       
      2017-05-05 18:40:02 5016 [ERROR] Plugin 'InnoDB' init function returned error.
       
      2017-05-05 18:40:02 5016 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
      

      Attachments

        Issue Links

          Activity

            People

              marko Marko Mäkelä
              elenst Elena Stepanova
              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.