mirror of
https://github.com/MariaDB/server.git
synced 2026-02-14 22:58:42 +01:00
14d9323f60
It was possible that a log checkpoint was completed and the server killed between the time that fil_ibd_create() durably wrote a FILE_CREATE record, and the initialization of the tablespace. This could lead to a failure to start up after the server was killed during TRUNCATE TABLE or any table-rebuilding operation such as OPTIMIZE TABLE. In the case of TRUNCATE TABLE, an attempt to rename a file #sql-ibNNN.ibd (the contents of the table before truncation) to tablename.ibd would fail, because both files existed and the file tablename.ibd would have been filled with NUL bytes. It was possible to resume from this error by deleting the file tablename.ibd and restarting the server. We will prevent this class of errors by ensuring that both the FILE_CREATE record and the records written by fsp_header_init() will be part of the same atomic transaction, which must be durably written before any file is created or allocated. NOTE: There is another possible crash recovery problem, which we are not attempting to solve here and which will be covered by the subsequent change (MDEV-38026). If fil_ibd_create() fails to create the file and the server were killed, recovery would not even attempt to create the file at all. fil_space_t::create(): Remove the DBUG_EXECUTE_IF fault injection that was the only cause of return nullptr. This allows us to simplify several callers. fil_space_t::set_stopped(), fil_space_t::clear_stopped(): Accessor functions for fil_ibd_create() for preventing any concurrent access to an incompletely created tablespace. fil_ibd_create(): In a single atomic mini-transaction, write the FILE_CREATE record as well as the log for initializing the tablespace. After durably writing the log, create the file in the file system Only after the file has been successfully created and allocated, open the tablespace for business. Finally, release the exclusive page latches so that the header pages may be written to the file. fil_ibd_open(): Move some fault injection from fil_space_t::create() to a higher level, to the place where an existing file is being opened. Reviewed by: Thirunarayanan Balathandayuthapani Tested by: Saahil Alam |
||
|---|---|---|
| .. | ||
| basic.result | ||
| bug_32831765.result | ||
| concurrent_insert.result | ||
| crash_recovery.result | ||
| create.result | ||
| foreign_key_check.result | ||
| foreign_key_update.result | ||
| ft_result_cache_limit.result | ||
| fts_kill_query.result | ||
| fts_sync_commit_resiliency.result | ||
| fulltext.result | ||
| fulltext2.result | ||
| fulltext3.result | ||
| fulltext_cache.result | ||
| fulltext_distinct.result | ||
| fulltext_left_join.result | ||
| fulltext_misc.result | ||
| fulltext_multi.result | ||
| fulltext_order_by.result | ||
| fulltext_update.result | ||
| fulltext_var.result | ||
| index_table.result | ||
| innodb-fts-ddl,vers.rdiff | ||
| innodb-fts-ddl,vers_trx.rdiff | ||
| innodb-fts-ddl.result | ||
| innodb-fts-fic,vers.rdiff | ||
| innodb-fts-fic,vers_trx.rdiff | ||
| innodb-fts-fic.result | ||
| innodb_ft_aux_table.result | ||
| innodb_fts_large_records.result | ||
| innodb_fts_misc.result | ||
| innodb_fts_misc_1.result | ||
| innodb_fts_multiple_index.result | ||
| innodb_fts_plugin.result | ||
| innodb_fts_proximity.result | ||
| innodb_fts_result_cache_limit.result | ||
| innodb_fts_stopword_charset.result | ||
| innodb_fts_transaction.result | ||
| limit_union.result | ||
| misc.result | ||
| misc_1.result | ||
| misc_debug,vers.rdiff | ||
| misc_debug,vers_trx.rdiff | ||
| misc_debug.result | ||
| misc_debug2.result | ||
| multiple_index.result | ||
| opt.result | ||
| phrase.result | ||
| plugin_debug.result | ||
| result_cache_limit.result | ||
| savepoint.result | ||
| stopword,vers.rdiff | ||
| stopword.result | ||
| subexpr.result | ||
| sync.result | ||
| sync_block.result | ||
| sync_ddl,vers.rdiff | ||
| sync_ddl,vers_trx.rdiff | ||
| sync_ddl.result | ||
| versioning,prepare.result | ||
| versioning.result | ||