When I try OPTIMIZE TABLE `table` (MyISAM) on a table which is about 300MB, then it is crashed and must be repaired. What could cause this problem? The same problem occurs on other tables over 300MB.

  • Did you try repairing the tables and retrying the OPTIMIZE?
    – nneonneo
    Commented Mar 31, 2013 at 9:02
  • please provide MySQL server version, also show your my.cnf without comments (on Linux it would be /etc/my.cnf).
    – mvp
    Commented Mar 31, 2013 at 9:02
  • Yes, after repair, optimize works. But next day, it crashs again. Commented Apr 3, 2013 at 4:21
  • can you provide your server config (pysical server like memory/disk), does the mysql error log display any message? Commented Apr 30, 2013 at 19:47

1 Answer 1


MYISAM tables are very fragile and get damaged/crash every now and then. First advice is to move to Innodb engine it is simply performed by using alter table command.

Now, to fix crashed MYISAM tables the proper way is to bring the MYSQL down and once it is down and there is no traffic you can fix them using this command line statement:

myisamchk --silent --force --fast  /path/table-name.MYI

Trying to repair/optimise MYISAM tables on a live server usually does not work. From MYSQL CLI the command should be

mysql> repair table tablename;

instead of optimize table if the table was crashed.

  • Table crashes after optimize table. InnoDB would be better, but this is table for fulltext search. Commented Apr 3, 2013 at 4:26

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.