Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Cannot Reproduce
-
10.1(EOL), 10.2(EOL)
-
None
Description
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;
|
Attachments
Issue Links
- relates to
-
MDEV-12699 Improve crash recovery of corrupted data pages
- Closed
-
MDEV-7069 Fix buildbot failures in main server trees
- Stalled