表信息：
Database name: user_motiva Table name: wp_options.frm wp_options.MYD wp_options.MYI wp_options.TMD
当我做一个MysqLcheck -r –all-databases时,即使你让它整天坐着,它也会挂在那个桌子上.即使只是一张支票挂在同一个地方.
有没有其他方法来修复/修复/恢复该表？
我应该使用myisamchk吗？我看到类似的东西：
shell> myisamchk --recover City
您甚至无法从PHPMyAdmin访问/查看数据库,甚至“USE”;在MysqL没有它只是挂.
我配置在一个16GB的ram盒子上
cat /etc/my.cnf [MysqLd] default-storage-engine=MyISAM local-infile=0 symbolic-links=0 skip-networking max_connections = 500 max_user_connections = 20 key_buffer = 512M myisam_sort_buffer_size = 64M join_buffer_size = 64M read_buffer_size = 12M sort_buffer_size = 12M read_rnd_buffer_size = 12M table_cache = 2048 thread_cache_size = 16K wait_timeout = 30 connect_timeout = 15 tmp_table_size = 64M max_heap_table_size = 64M max_allowed_packet = 64M max_connect_errors = 10 query_cache_limit = 1M query_cache_size = 64M query_cache_type = 1 low_priority_updates=1 concurrent_insert=ALWAYS log-error=/var/log/MysqL/error.log tmpdir=/home/MysqLtmp myisam_repair_threads=4 [MysqLd_safe] open_files_limit = 8192 log-error=/var/log/MysqL/error.log [MysqLdump] quick max_allowed_packet = 512M [myisamchk] key_buffer = 64M sort_buffer = 64M read_buffer = 16M write_buffer = 16M
这是因为killall -9 MysqLd崩溃了,因为它不会关闭并重启？
编辑：
root@server [/var/lib/MysqL/user_motiva]# myisamchk -e *.MYI Checking MyISAM file: wp_options.MYI Data records: 1827 Deleted blocks: 3 myisamchk: warning: 3 clients are using or haven't closed the table properly - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check data record references index: 2 - check records and index references MyISAM-table 'wp_options.MYI' is usable but should be fixed root@server [/var/lib/MysqL/user_motiva]# myisamchk --safe-recover wp_options.MYI - recovering (with keycache) MyISAM-table 'wp_options.MYI' Data records: 1827 myisamchk: error: Can't create new tempfile: 'wp_options.TMD' MyISAM-table 'wp_options.MYI' is not fixed because of errors Try fixing it by using the --safe-recover (-o),the --force (-f) option or by not using the --quick (-q) flag root@ns2 [/var/lib/MysqL/user_motiva]# myisamchk -o -f wp_options.MYI - recovering (with keycache) MyISAM-table 'wp_options.MYI' Data records: 1827
这是否意味着它现在已修复？如果是这样,我该如何将其移回？ (这是在不同的服务器上完成的)
有没有办法让MysqL在主服务器上运行并运行命令来修复所有文件？
