Bug #74772 | Running REPAIR TABLE [table] EXTENDED Causes MySQL to Restart Constantly | ||
---|---|---|---|
Submitted: | 10 Nov 2014 21:53 | Modified: | 16 Apr 2018 12:47 |
Reporter: | Gino Williams | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Partitions | Severity: | S3 (Non-critical) |
Version: | 5.5.18-log | OS: | Solaris |
Assigned to: | CPU Architecture: | Any | |
Tags: | archive, partitions |
[10 Nov 2014 21:53]
Gino Williams
[11 Nov 2014 23:52]
MySQL Verification Team
Thank you for the bug report. Could you please check this issue with most recent released version 5.5.40?. Thanks.
[11 Nov 2014 23:52]
MySQL Verification Team
Thank you for the bug report. Could you please check this issue with most recent released version 5.5.40?. Thanks.
[12 Nov 2014 0:08]
MySQL Verification Team
Sorry I forgot to ask you to check in the server log-error a call stack of probably server crash. Thanks.
[12 Nov 2014 18:58]
Gino Williams
The problem was the same on 5.5.40. We created a new instance on a completely separate box to make sure that we were not upgrading MySQL on a possibly damaged hardware. Error logs did not show anything running during the restart other than the REPAIR TABLE statement. It appears that there was a particular partition that was irreparably damaged. I dropped that partition, which allowed access to the table without initiating a repair behind the scenes. I reloaded the data for the date range (per the dropped partition) from raw files. No other partitions were corrupted. As a precautionary, I performed a full repair to completion without any restarts on the MySQL instance. Clearly, a partition can become so corrupted that a repair will not work and may cause restarts to the MySQL instance during a repair or rebuild of a partition. Unfortunately, recovery in this instance may have to be manually intensive.
[24 Nov 2014 19:55]
Gino Williams
Is it possible that a partition can indeed become so corrupted that a full repair will never work? If this is the case, then I need to come up with a plan for replacing MySQL with a RDBMS that does both partitioning and table compression.
[16 Apr 2018 12:47]
MySQL Verification Team
Hi, The answer to your question is positive. If a disk or partition gets corrupted, then there is no cure for your tables, unless you have a backup. The only storage engine that is constantly checking whether data was written properly to the disk is our InnoDB storage engine. Provided, you do not turn off all the security settings, like double writing or similar. Hence, that is our advice to you. Switch to InnoDB SE. Our manual has all explanations on how to do it and how to tune that engine.