Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL)
Description
While MDEV-28870 reduced the failure probability of test atomic.rename_table, the test still occasionally fails, especially on the kvm-ubsan builder. Here is the relevant part of one failure:
10.6 0fa19fdebf0925be6ec5503938d541332f259cb5 |
CURRENT_TEST: atomic.rename_table
|
mysqltest: At line 155: query 'let $res=`select t1.a+t2.b+t3.c+t4.d from t1,t2,t3,t4`' failed: ER_UNKNOWN_STORAGE_ENGINE (1286): Unknown storage engine 'InnoDB'
|
…
|
2022-06-22 8:00:48 0 [ERROR] InnoDB: Tablespace 5 was not found at ./test/t5.ibd.
|
2022-06-22 8:00:48 0 [ERROR] InnoDB: Set innodb_force_recovery=1 to ignore this and to permanently lose all changes to the tablespace.
|
2022-06-22 8:00:48 0 [ERROR] InnoDB: Plugin initialization aborted at srv0start.cc[1447] with error Tablespace not found
|
I would need at least a copy of a data directory that failed to recover. Preferrably from 10.8 or a later branch, because the MDEV-14425 log file format is easier to read, thanks to the lack of any block framing. An rr record trace of the killed server could significantly ease the analysis.
Attachments
Issue Links
- is blocked by
-
MDEV-27111 atomic.rename_table test case fails on bb-10.6-MDEV-27022 branch
- Closed
-
MDEV-28870 InnoDB: Missing FILE_CREATE, FILE_DELETE or FILE_MODIFY before FILE_CHECKPOINT during crash recovery
- Closed
- is caused by
-
MDEV-24626 Remove synchronous write of page0 and flushing file during file creation
- Closed