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

innodb.leaf_page_corrupted_during_recovery failed in buildbot with Warning Data too long for column

Details

    Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-asan/builds/1453

      bb-10.3-release 1135244a647e423f6a7b2122ad9c3052

      		 
      nnodb.leaf_page_corrupted_during_recovery 'innodb' w1 [ fail ]  Found warnings/errors in server log file!
      		 
              Test ended at 2019-06-14 10:50:28
      		 
      Warnings:
      		 
      Warning	1406	Data too long for column 'line' at row 10
      		 
      line
      		 
       len 16384; hex 6a756e6b000000130000000effffffff000000000019399345bf0000000000000000000000050002018e800300000000007e0005000000010000000000000000000000000000000000190000000000000000000000000000000000000000010002001b696e66696d756d0002000b000073757072656d756d00000010fff28000000c0000000000008000000000000074657374382020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
      		 
      ^ Found warnings in /dev/shm/var/1/log/mysqld.1.err

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-28389 Data too long for column 'line'

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            marko Marko Mäkelä added a comment -

            I did not see anything special in the server error log. Perhaps the page dump output was not interleaved with other output in this case?

            Do we actually need the dumps of corrupted pages when reporting a read error? Shouldn’t the file name and page number be enough output?

            marko Marko Mäkelä added a comment - I did not see anything special in the server error log . Perhaps the page dump output was not interleaved with other output in this case? Do we actually need the dumps of corrupted pages when reporting a read error? Shouldn’t the file name and page number be enough output?
            marko Marko Mäkelä added a comment -

            Since this test is using debug instrumentation, we will solve the issue by disabling page dumps in debug builds altogether. Users of debug builds will likely know how to extract page dumps in other means.

            Page dump output could sometimes be useful when diagnosing problems that users are facing. Hence we will keep the page dump output in non-debug (release) builds.

            marko Marko Mäkelä added a comment - Since this test is using debug instrumentation, we will solve the issue by disabling page dumps in debug builds altogether. Users of debug builds will likely know how to extract page dumps in other means. Page dump output could sometimes be useful when diagnosing problems that users are facing. Hence we will keep the page dump output in non-debug (release) builds.

            People

              thiru Thirunarayanan Balathandayuthapani
              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.