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

innodb.log_data_file_size fails on buildbot with warnings intermittently

Details

    Description

      From
      http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/5412/steps/test/logs/stdio

      innodb.log_data_file_size '16k,xtradb' w1 [ fail ] Found warnings/errors in server log file!
      Test ended at 2017-09-16 00:13:01
      line
      2017-09-16 0:12:59 4080 [Warning] InnoDB: A copy of page 4:4 in the doublewrite buffer slot 13 is not within space bounds

      2017-09-16 0:12:59 4080 [Warning] InnoDB: A copy of page 5:4 in the doublewrite buffer slot 19 is not within space bounds

      2017-09-16 0:13:00 2392 [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-09-16 0:13:00 2392 [ERROR] InnoDB: Read operation failed for tablespace ./test/ibd4f.ibd offset 4 with error Page read from tablespace is corrupted.

      2017-09-16 0:13:01 4080 [ERROR] Plugin 'InnoDB' init function returned error.

      2017-09-16 0:13:01 4080 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

      ^ Found warnings in D:/win32-debug/build/mysql-test/var/1/log/mysqld.1.err
      ok

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MDEV-12893 innodb.log_data_file_size failed in buildbot with InnoDB: Database page corruption

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-12699 Improve crash recovery of corrupted data pages

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            elenst Elena Stepanova added a comment -

            Duplicate of MDEV-12893

            elenst Elena Stepanova added a comment - Duplicate of MDEV-12893
            marko Marko Mäkelä added a comment -

            My fix introduced another intermittent test failure (actually, exposing MDEV-12699).

            2017-09-18 10:43:11 0 [Note] InnoDB: Recovered page [page id: space=0, page number=322] from the doublewrite buffer.
            		 
            2017-09-18 10:43:16 0 [Note] InnoDB: Starting final batch to recover 25 pages from redo log.
            		 
            2017-09-18 10:43:16 0 [Note] InnoDB: Log sequence number at the start 3129101 and the end 0 do not match
            		 
            2017-09-18 10:43:16 0 [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.

            The test is truncating this page to 1234 bytes. Apparently what happens is that the file will be zero-padded to the correct length, and subsequently we will read a corrupted page (the first 1234 bytes are correct; the remaining bytes are 0).

            To work around MDEV-12699, the test must set those 1234 bytes to zeroes, so that the subsequent startup will see a valid-looking all-zero page after extending the file.

            marko Marko Mäkelä added a comment - My fix introduced another intermittent test failure (actually, exposing MDEV-12699 ). 2017-09-18 10:43:11 0 [Note] InnoDB: Recovered page [page id: space=0, page number=322] from the doublewrite buffer. 2017-09-18 10:43:16 0 [Note] InnoDB: Starting final batch to recover 25 pages from redo log. 2017-09-18 10:43:16 0 [Note] InnoDB: Log sequence number at the start 3129101 and the end 0 do not match 2017-09-18 10:43:16 0 [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. The test is truncating this page to 1234 bytes. Apparently what happens is that the file will be zero-padded to the correct length, and subsequently we will read a corrupted page (the first 1234 bytes are correct; the remaining bytes are 0). To work around MDEV-12699 , the test must set those 1234 bytes to zeroes, so that the subsequent startup will see a valid-looking all-zero page after extending the file.

            People

              marko Marko Mäkelä
              wlad Vladislav Vaintroub
              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.