MySQL Bugs: #64977: Four Data Files with Incorrect Key File after 5.6.5m7 to 5.6.5m8 update

Bug #64977	Four Data Files with Incorrect Key File after 5.6.5m7 to 5.6.5m8 update
Submitted:	14 Apr 2012 3:09	Modified:	10 Jan 2013 14:27
Reporter:	George Gruber	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S1 (Critical)
Version:	5.6.5m8	OS:	Windows (Windows 7 x64)
Assigned to:		CPU Architecture:	Any

Description:
Upgrading from 5.6m7 to 5.6m8 has caused four tables to return the error:
Incorrect key file for table 'common_terms'; try to repair it.

The installation seemed to go along smoothly enough (there was an issue that required adding skip-slave-start and was able to update those files to eliminate the issue).  However, after starting back up I ran mysql_upgrade.exe and I received the above errors and it seemed like it tried a repair and it failed.  I have tried numerous methods of repair including myisamchk -r -q, -r, -o and REPAIR TABLE file USE_FRM and these caused MySQL to actually crash.

I was able to get a dump one of the tables and was able to rebuild it by using DROP TABLE and inserting all of the records into that table.

So what could be so wrong that myisamchk and REPAIR TABLE fail to repair (and causes MySQL to crash)?  Why are these errors occurring in this update?

How to repeat:
I do not know if it is repeatable beyond my own set of tables.  I have similar tables running on two different computers and upgrading both machines caused the same tables to show the same errors.  I would be happy to provide my tables.

It is the two latest versions of 5.6 - 5.6.5m7 and m8.

Thank you for the bug report. Could you please provide the dump file of the table so I can create it with older Server version and then upgrade to 5.6.5m8. Thanks.

I apologize for the delay but I was out of town when you sent me the request.  Just for my own sanity I went back and re-ran mysqlcheck.exe against the database and m7 shows no error and m8 shows an error with no means to fix it.  I have uploaded one of the four tables (common_terms).  What I have not done was tried to rebuild that table in m7 first which is why I uploaded a zip file with both a SQL file to rebuild it from scratch and the m7 copy of the MYD, MYI and frm files.

Thank you!

Thank you for the files.

I could repeat corruption using dump, but could not repeat crash. Also REPAIR EXTENDED USE_FRM fixed the table for me.

But I still think this can be considered as upgrade bug and such incompatibility should be at least documented at http://dev.mysql.com/doc/refman/5.6/en/news-5-6-5.html

[1 Sep 2012 7:41] Paul Dubois (PDUBOIS)
Closed as a duplicate of an internally filed bug.

Milestone release changelog sections now have this preamble:

Note:
This is a milestone release, for use at your own risk. Significant
development changes take place in milestone releases and you may encounter
compatibility issues, such as data format changes that require attention in
addition to the usual procedure of running mysql_upgrade. For example, you
may find it necessary to dump your data with mysqldump before the upgrade and
reload it afterward.

Sorry, not a duplicate, but a documenation issue. My bad.