[MDEV-32445] InnoDB may corrupt its log before upgrading it on startup Created: 2023-10-11  Updated: 2023-10-11

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.5, 10.6, 10.7, 10.8, 10.9, 10.10, 10.11, 11.0, 11.1, 11.2, 11.3
Fix Version/s: 10.5, 10.6, 10.11, 11.0, 11.1, 11.2, 11.3

Type: Bug Priority: Critical
Reporter: Marko Mäkelä Assignee: Thirunarayanan Balathandayuthapani
Resolution: Unresolved Votes: 0
Labels: corruption, upgrade

Issue Links:
Relates
relates to MDEV-12353 Efficient InnoDB redo log record format Closed
relates to MDEV-14425 Change the InnoDB redo log format to ... Closed

 Description   

In the function srv_start(), there are some optional adjustments for MDEV-11623 as well as something related to innodb_data_file_path. These adjustments would write log records, even though the log has not yet been upgraded to the configured format (create_log_file_rename()).

For example, killing the server at an unfortunate time during an upgrade from 10.1 could theoretically make the data directory unrecoverable.

I think that we must try to cover this code in our regression tests. There should already be a debug assertion for catching writes to a wrong-format log file.


Generated at Thu Feb 08 10:31:25 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.