An marked as crashed and last (automatic?) repair failed solution appears after the table is optimized

An marked as crashed and last (automatic?) repair failed appears after the table is optimized
Today, to optimize the table, the following problems occurred after optimization:

SQL Code

  mysql> OPTIMIZE TABLE jo_mailqueue;+---------------------+----------+----------+------------------------------ -------------------------------+| Table | Op | Msg_type | Msg_text |+---------------------+-- --------+----------+-------------------------------------------------------------+| Jobour.jo_mailqueue | Optimize | Error | 1 when fixing table | | Jobour.jo_mailqueue | Optimize | Error | Can ' t change ownership of the file '/usr/local/mysql/data/jobour/jo_mailqueue. MYD ' (errcode:1) | | Jobour.jo_mailqueue | Optimize | Status | Operation failed |+---------------------+-- --------+----------+---------------------------------------------------

After opening from phpMyAdmin, the discovery table is in use.


OPTIMIZE Optimization Table How can this problem occur ah. What caused it.? Thank you!






------Solution--------------------
The index is broken, MyISAM is always so rotten. Repairing REPAIR TABLE with commands

