[MDEV-15671] innodb.recovery_shutdown failed in buildbot with Checksum mismatch in datafile Created: 2018-03-26  Updated: 2023-05-29  Resolved: 2023-05-29

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB, Tests
Affects Version/s: 10.0, 10.2
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-18128 Simplify .ibd file creation Closed

 Description   

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

innodb.recovery_shutdown 'innodb'        w2 [ fail ]  Found warnings/errors in server log file!
 
        Test ended at 2018-02-19 05:09:29
 
line
 
2018-02-19  5:09:24 140283517974400 [ERROR] InnoDB: Checksum mismatch in datafile: ./test/t.ibd, Space ID:67, Flags: 33. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
 
^ Found warnings in /dev/shm/var/2/log/mysqld.1.err
 
ok



 Comments   
Comment by Elena Stepanova [ 2018-04-26 ]

Failure on 10.0, possibly related:

10.0 400a8eb60f832030a04a248e2c96552a

 
innodb.recovery_shutdown 'innodb_plugin' w2 [ fail ]  Found warnings/errors in server log file!
 
        Test ended at 2018-04-06 13:05:45
 
line
 
InnoDB: Warning: database page corruption or a failed
 
^ Found warnings in /usr/local/mariadb-10.0.35-linux-i686/mysql-test/var/2/log/mysqld.1.err
 
ok
 
 
 
 - saving '/usr/local/mariadb-10.0.35-linux-i686/mysql-test/var/2/log/innodb.recovery_shutdown-innodb_plugin/' to '/usr/local/mariadb-10.0.35-linux-i686/mysql-test/var/log/innodb.recovery_shutdown-innodb_plugin/'
 
 
 
Retrying test innodb.recovery_shutdown, attempt(2/3)...
 
 
 
worker[2] > Restart  - not started

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

My best guess is that this could be fixed by MDEV-18128. The test is killing and restarting InnoDB soon after some data files were created.

The log files are no longer available, so I cannot verify my claim.

Comment by Marko Mäkelä [ 2023-05-29 ]

I think that this particular failure has been fixed. Recent failures (which are rare) have been due to something else, such as a hang in innodb_preshutdown(), or recovery taking a too long time when running under Valgrind.

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