Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.6
-
None
Description
encryption.innodb-redo-badkey test case is failing occasionally in buildbot with
the following error:
2026-01-09 5:39:03 0 [ERROR] InnoDB: The first page of file ./test/t3.ibd is corrupted
|
2026-01-09 5:39:03 0 [ERROR] InnoDB: The first page of file ./test/t3.ibd is corrupted
|
2026-01-09 5:39:03 0 [ERROR] InnoDB: The first page of file ./test/t3.ibd is corrupted
|
2026-01-09 5:39:03 0 [ERROR] InnoDB: The first page of file ./test/t3.ibd is corrupted
|
2026-01-09 5:39:03 0 [ERROR] InnoDB: The first page of file ./test/t3.ibd is corrupted
|
Test case where we noticed this error is that starting the server with incorrect encrypted keys.
Also page0 shouldn't be all zero at all. Because we do force checkpoint before killing
the server. Page0 is not encrypted. So wrong encryption key shouldn't play any role for page0
update t3 set c = repeat('secret4', 20);
|
update t4 set c = repeat('secret4', 20);
|
insert into t1 (c,b) values (repeat('secret5',20), repeat('secret6',6000));
|
insert into t2 (c,b) values (repeat('secret7',20), repeat('secret8',6000));
|
insert into t3 (c,b) values (repeat('secret9',20), repeat('secre10',6000));
|
insert into t4 (c,b) values (repeat('secre11',20), repeat('secre12',6000));
|
COMMIT;
|
let $cleanup= drop table t1,t2,t3,t4;
|
--let CLEANUP_IF_CHECKPOINT= $cleanup;
|
--source ../../suite/innodb/include/no_checkpoint_end.inc
|
 |
--error 1
|
-- source include/start_mysqld.inc
|
--source include/kill_mysqld.inc
|
|
Attaching the error log just to prove the first restart works fine.
Cross reference throws same error happened in last year. Sometimes, table t4
is corrupted message as well.
[Cross reference failure|
https://buildbot.mariadb.net/ci/reports/cross_reference#branch=&revision=&platform=&fail_name=encryption.innodb-redo-badkey&fail_variant=&fail_info_full=The+first+page+of+file&typ=&info=&dt=&limit=100&fail_info_short=]