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

rpl.rpl_gtid_crash failed in buildbot with Warning: database page corruption or a failed

        Details

        • Type: Bug
        • Status: Closed
        • Priority: Minor
        • Resolution: Fixed
        • Affects Version/s: 10.1, 10.0
        • Fix Version/s: 10.0.16, 10.1.2
        • Component/s: Tests
        • Labels:

          Description

          It happened once so far:
          http://buildbot.askmonty.org/buildbot/builders/bld-dan-debug/builds/1651/steps/test/logs/stdio

          rpl.rpl_gtid_crash 'innodb_plugin,stmt'  w2 [ fail ]  Found warnings/errors in server log file!
        Test ended at 2014-11-23 12:48:11
line
InnoDB: Warning: database page corruption or a failed
^ Found warnings in /opt/buildbot-slave/mariadb/dan_demeter1/build/mysql-test/var/2/log/mysqld.1.err
ok

            Gliffy Diagrams

              Attachments

                Issue Links

                relates to

                Bug - A problem which impairs or prevents the functions of the product. MDEV-7491 Occasional test failure in innodb.group_commit_crash_no_optimize_thread

                • Major - Major loss of function.
                • Closed

                Task - A task that needs to be done. MDEV-7172 Fix buildbot failures in 10.1 tree

                • Major - Major loss of function.
                • Closed

                  Activity

                  Ascending order - Click to sort in descending order
                  Hide
                  Permalink
                  knielsen Kristian Nielsen added a comment -

                  Seen two times in 10.0 trees also:

                  http://buildbot.askmonty.org/buildbot/reports/cross_reference#branch=&revision=&platform=&dt=&bbnum=&typ=&info=&fail_name=rpl.rpl_gtid_crash&fail_variant=&fail_info_short=&fail_info_full=database+page+corruption+or+a+failed&limit=100

                  The warning in the error log looks like this:

                  141123 12:47:54 [Note] InnoDB: Restoring possible half-written data pages 
141123 12:47:54 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Warning: database page corruption or a failed
InnoDB: file read of space 6 page 3.
InnoDB: Trying to recover it from the doublewrite buffer.
141123 12:47:54 [Note] InnoDB: Recovered the page from the doublewrite buffer.

                  So there is a half-written page, but it is recovered correctly from the
                  double-write buffer. Since we deliberately crash the server in the test case,
                  half-written pages is not unexpected. So I added a suppression for this
                  warning in the test case.

                  Show
                  knielsen Kristian Nielsen added a comment - Seen two times in 10.0 trees also: http://buildbot.askmonty.org/buildbot/reports/cross_reference#branch=&revision=&platform=&dt=&bbnum=&typ=&info=&fail_name=rpl.rpl_gtid_crash&fail_variant=&fail_info_short=&fail_info_full=database+page+corruption+or+a+failed&limit=100 The warning in the error log looks like this: 141123 12:47:54 [Note] InnoDB: Restoring possible half-written data pages 141123 12:47:54 [Note] InnoDB: from the doublewrite buffer... InnoDB: Warning: database page corruption or a failed InnoDB: file read of space 6 page 3. InnoDB: Trying to recover it from the doublewrite buffer. 141123 12:47:54 [Note] InnoDB: Recovered the page from the doublewrite buffer. So there is a half-written page, but it is recovered correctly from the double-write buffer. Since we deliberately crash the server in the test case, half-written pages is not unexpected. So I added a suppression for this warning in the test case.
                  Hide
                  Permalink
                  knielsen Kristian Nielsen added a comment -

                  Same issue applies to innodb.group_commmit_crash and innodb.group_commit_crash_no_optimize_thread

                  Show
                  knielsen Kristian Nielsen added a comment - Same issue applies to innodb.group_commmit_crash and innodb.group_commit_crash_no_optimize_thread

                    People

                    • Assignee:
                      knielsen Kristian Nielsen
                      Reporter:
                      elenst Elena Stepanova
                    • Votes:
                      0 Vote for this issue
                      Watchers:
                      1 Start watching this issue

                      Dates

                      • Created:
                        Updated:
                        Resolved: