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

innodb.innodb_bug14147491 sporadically fails in buildbot due to wrong error number

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.1(EOL)
    • 10.1.24, 10.2.6
    • Tests
    • None

    Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-deb-jessie-amd64/builds/2094/steps/mtr/logs/stdio

      innodb.innodb_bug14147491 'innodb_plugin' w1 [ fail ]
              Test ended at 2017-04-27 17:07:58
       
      CURRENT_TEST: innodb.innodb_bug14147491
      mysqltest: At line 76: query 'SELECT * FROM t1' failed with wrong errno 1712: 'Index t1 is corrupted', instead of 1932...
       
      The result from queries just before the failure was:
      call mtr.add_suppression("InnoDB: Table \"test\".\"t1\" is corrupted. Please drop the table and recreate.");
      call mtr.add_suppression("InnoDB: Cannot open table test/t1 from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.");
      call mtr.add_suppression("InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page  \[page id: space=[0-9]+, page number=[0-9]+\]. You may have to recover from a backup.");
      # Create and populate the table to be corrupted
      set global innodb_file_per_table=ON;
      CREATE TABLE t1 (a INT AUTO_INCREMENT PRIMARY KEY, b TEXT) ENGINE=InnoDB;
      INSERT INTO t1 (b) VALUES ('corrupt me');
      INSERT INTO t1 (b) VALUES ('corrupt me');
      # Backup the t1.ibd before corrupting
      # Corrupt the table
      Munged a string.
      Munged a string.
      # The below SELECT query will return that table is not
      # in engine because table is corrupted
      SELECT * FROM t1;
       
      Warnings from just before the error:
      Warning 180 InnoDB: Index "PRIMARY" for table "test"."t1" is marked as corrupted
      

      Attachments

        Issue Links

          Activity

            This is a regression from MDEV-12253.

            marko Marko Mäkelä added a comment - This is a regression from MDEV-12253 .

            10.1: commit e1efeaa5502f640102881f415d604cc10fbf54a9
            Author: Jan Lindström <jan.lindstrom@mariadb.com>
            Date: Mon May 8 12:04:08 2017 +0300

            MDEV-12628: innodb.innodb_bug14147491 sporadically fails in buildbot due to wrong error number

            Actual error number returned from the query depends what point
            corrupted page is accessed, is it accessed when we read
            one of the pages for result set or is it accessed during
            background page read.

            jplindst Jan Lindström (Inactive) added a comment - 10.1: commit e1efeaa5502f640102881f415d604cc10fbf54a9 Author: Jan Lindström <jan.lindstrom@mariadb.com> Date: Mon May 8 12:04:08 2017 +0300 MDEV-12628 : innodb.innodb_bug14147491 sporadically fails in buildbot due to wrong error number Actual error number returned from the query depends what point corrupted page is accessed, is it accessed when we read one of the pages for result set or is it accessed during background page read.

            10.2: commit f0eb8f153d55305e43a43e6fa604418fc406fd48
            Author: Jan Lindström <jan.lindstrom@mariadb.com>
            Date: Mon May 8 12:04:08 2017 +0300

            MDEV-12628: innodb.innodb_bug14147491 sporadically fails in buildbot due to wrong error number

            Actual error number returned from the query depends what point
            corrupted page is accessed, is it accessed when we read
            one of the pages for result set or is it accessed during
            background page read.

            jplindst Jan Lindström (Inactive) added a comment - 10.2: commit f0eb8f153d55305e43a43e6fa604418fc406fd48 Author: Jan Lindström <jan.lindstrom@mariadb.com> Date: Mon May 8 12:04:08 2017 +0300 MDEV-12628 : innodb.innodb_bug14147491 sporadically fails in buildbot due to wrong error number Actual error number returned from the query depends what point corrupted page is accessed, is it accessed when we read one of the pages for result set or is it accessed during background page read.

            People

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