[MDEV-11808] innodb.innodb_bug14147491 failed in buildbot Created: 2017-01-15  Updated: 2020-08-21  Resolved: 2020-08-21

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.1, 10.2
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Marko Mäkelä
Resolution: Cannot Reproduce Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-12699 Improve crash recovery of corrupted d... Closed
relates to MDEV-7069 Fix buildbot failures in main server ... Stalled

 Description   

http://buildbot.askmonty.org/buildbot/builders/p8-rhel6-bintar-debug/builds/463/steps/test/logs/stdio

innodb.innodb_bug14147491 'xtradb'       w3 [ fail ]
        Test ended at 2016-12-23 02:29:28
 
CURRENT_TEST: innodb.innodb_bug14147491
mysqltest: At line 109: query 'SELECT * FROM t1' succeeded - should have failed with errno 2013...
 
The result from queries just before the failure was:
< snip >
CALL mtr.add_suppression("InnoDB: See also .* about forcing recovery.");
# Create and populate the table to be corrupted
CREATE TABLE t1 (a INT AUTO_INCREMENT PRIMARY KEY, b TEXT) ENGINE=InnoDB;
INSERT INTO t1 (b) VALUES ('corrupt me');
INSERT INTO t1 (b) VALUES ('corrupt me');
# Write file to make mysql-test-run.pl expect the "crash", but don't
# start it until it's told to
# We give 30 seconds to do a clean shutdown because we do not want
# to redo apply the pages of t1.ibd at the time of recovery.
# We want SQL to initiate the first access to t1.ibd.
# Wait until disconnected.
# Backup the t1.ibd before corrupting
# Corrupt the table
# Write file to make mysql-test-run.pl start up the server again
SET DEBUG_DBUG = '+d,innodb_page_corruption_retries';
# Write file to make mysql-test-run.pl expect the "crash", but don't
# start it until it's told to
# The below SELECT query will crash the server because some pages
# on the disk are corrupted
SELECT * FROM t1;



 Comments   
Comment by Elena Stepanova [ 2017-05-09 ]

Recent failure in 10.2:
http://buildbot.askmonty.org/buildbot/builders/winx64-packages/builds/3329/steps/test/logs/stdio

innodb.innodb_bug14147491 'innodb'       w2 [ fail ]  Found warnings/errors in server log file!
        Test ended at 2017-05-09 13:54:19
line
2017-05-09 13:54:17 692 [ERROR] mysqld.exe: Index for table 't1' is corrupt; try to repair it

Comment by Marko Mäkelä [ 2017-05-09 ]

Likely fixed by this commit.

In MDEV-12699 I would like to rewrite this test.

Comment by Marko Mäkelä [ 2020-08-21 ]

In the cross-reference, the latest failure of this test in a main branch is 10.1 afbd45a791a4a8cde19e0b3d5b883f79 on 2018-04-06, and that failure is different, and only occurring on Windows.

The last non-10.1 (and non-Windows) failure was 10.3 b81a403e69feadc9896893ddcddc35e8 on 2018-03-28 on kvm-fulltest.

I think that we can declare this bug fixed. MDEV-12699 was fixed in 2019 and made these failures much less likely. It should still be able occur, due to MDEV-20755.

In any case, we can declare this particular test failure as fixed.

Generated at Thu Feb 08 07:52:48 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.