[MDEV-19766] innodb.leaf_page_corrupted_during_recovery failed in buildbot with Warning Data too long for column Created: 2019-06-14  Updated: 2023-05-16  Resolved: 2019-07-01

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB, Tests
Affects Version/s: 10.3
Fix Version/s: 10.2.26, 10.3.17, 10.4.7

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Thirunarayanan Balathandayuthapani
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-28389 Data too long for column 'line' Closed

 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



 Comments   
Comment by Marko Mäkelä [ 2019-06-17 ]

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?

Comment by Marko Mäkelä [ 2019-07-01 ]

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.

Generated at Thu Feb 08 08:54:12 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.