全部:
mysqlcheck -A -o -r -p -uroot

指定数据库:
mysqlcheck -A -o -r 数据库名 -p


-r 恢复模式 -q 快速恢复
myisamchk -r tbl_name/*.MYI
myisamchk -r -q tbl_name/*.MYI

安全恢复
myisamchk --safe-recover tbl_name/*.MYI

quick参数做修补的工作：
linux# myisamchk --recover --quick tbl_name
linux# isamchk --recover --quick tbl_name
如果上面的方法不能解决问题，可以将--quick参数去掉：
linux# myisamchk --recover tbl_name
linux# isamchk --recover tbl_name
如果还是不能解决问题，可以再试着改用--safe_recover参数:
linux# myisamchk --safe_recover --quick tbl_name
linux# isamchk --safe_recover --quick tbl_name

附加MYSQL可怕的错误：
mysqld got signal 11;
The manual section 'Debugging a MySQL server' tells you how to
use a stack trace and/or the core file to produce a readable
backtrace that may help in finding out why mysqld died
Attempting backtrace. You can use the following information
to find out where mysqld died.  If you see no messages after
this, something went terribly wrong...
stack range sanity check, ok, backtrace follows
0x40077552
0x81281a0
0x8128f47
0x8127be0
0x8127995
0x8104947
0x80ff28f
0x810131b
0x80ee4bc
0x80c3c91
0x80c6b43
0x80c1fd9
0x80c1686

http://dev.mysql.com/doc/refman/5.0/en/using-stack-trace.html