When a server subsystem tries to access a corrupted table,
the server may crash.
If this outcome is not desirable when a corrupted table is encountered,
set the new system innodb_corrupt_table_action variable
to a value which allows the ongoing operation to continue
without crashing the server.
The server error log registers attempts to access corrupted table pages.
Interacting with the innodb_force_recovery variable
The innodb_corrupt_table_action variable
may work in conjunction with the innodb_force_recovery variable
which considerably reduces
the effect of InnoDB subsystems
running in the background.
If the innodb_force_recovery variable is set to a low value
and you expect the server to crash,
it may still be running due to
a non-default value of the innodb_corrupt_table_action variable.
For more information about the innodb_force_recovery variable,
see Forcing InnoDB Recovery
from the MySQL Reference Manual.
This feature adds a new system variable.
innodb_corrupt_table_action¶| Command Line: | Yes |
|---|---|
| Config File: | Yes |
| Scope: | Global |
| Dynamic: | Yes |
| Variable Type: | ULONG |
| Range: | assert, warn, salvage |
warn value is used it will pass corruption of the table as corrupt table instead of crashing itself. For this to work innodb_file_per_table should be enabled. All file I/O for the datafile after detected as corrupt is disabled, except for the deletion.salvage, XtraDB allows read access to a corrupted tablespace, but ignores corrupted pages”.
For general inquiries, please send us your question and someone will contact you.
