The project encountered this problem and continued operation after the disk was full, causing the table to be indexed incorrectly.
phpMyAdmin has a repair button, but the project is using MySQL front software in a Windows environment. Online on the repair of the fault answer, in the actual operation is still a bit biased, so the process recorded.
After locating the Myisamchk.exe path (C:\mysql5.6\MySQL Server 5.6\bin), run the Myisamchk-c-R path directly, for example:
C:\mysql5.6\MySQL Server 5.6\bin>myisamchk-c-R D:\database\mysql5.6\data\dbname\tablename
Online there are answers saying run myisamchk-c-R D:\database\mysql5.6\data\dbname\tablename. MYI
The result is a myisam-table of the wrong ...
The fixes are as follows:
Data records:163763
-Fixing Index 1
Found link, points at 18337776 (outside data file) at 8461788
-Fixing Index 2
Data records:163762
This article is from the "Flying Potato God teach" blog, please be sure to keep this source http://1105190775.blog.51cto.com/10048144/1880287
MySQL "is marked as crashed and should be repaired" fault