Hello monty, I'm using mysql 3.23.32 on linux and it looks like there is a problem with check/auto-recovery left: On many of my servers I find the above in a log file: 24.Jan 23:45:07 : pid:1412 counter:32256 AllInOne MySqlEr Query - #1034 [tor.local] - Incorrect key file for table: 'g09stat_sitepaths'. Try to repair it delete from layers_st37.g09stat_sitepaths where layer_id=14704 24.Jan 23:45:07 : pid:1412 h -- 32256/0 AllInOne rec:290 l:0 tm:4.03 24.Jan 23:45:07 : pid:1412 h 32256/0 [24.1 1:42] - [] q:0.23 i:0.00 a:3.32 Then I look to the .err log file I se there : tor:/spylog/layers # tail -10000 /spylog/db/tor.err | grep g09stat_sitepaths 010124 2:13:46 Warning: Checking table: './layers_st26/g09stat_sitepaths' 010124 2:17:10 Warning: Checking table: './layers_st38/g09stat_sitepaths' 010124 3:10:08 Warning: Checking table: './layers_st37/g09stat_sitepaths' 010124 9:17:48 Warning: Checking table: './layers_st49/g09stat_sitepaths' So the table was checked and was found OK. Then I do check table now: mysql> check table layers_st37.g09stat_sitepaths; +-------------------------------+-------+----------+----------------------------+ | Table | Op | Msg_type | Msg_text | +-------------------------------+-------+----------+----------------------------+ | g09stat_sitepaths | check | warning | Table is marked as crashed | | layers_st37.g09stat_sitepaths | check | status | OK | +-------------------------------+-------+----------+----------------------------+ 2 rows in set (9.11 sec) So it is still marked crashed were it's really OK and even more it was checked and found correct before. -- Best regards, Peter mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
