Re: Incorrect key file for table 'XXX.MYI'; try to repair it

[Hava Ba]

Hi Rick,
Thanks for the replay. The problem occurred at two different servers, and I have additional quastions regarding each one of them.

First one did restart itself
============================
And it may cause the corruption, maybe mysql didn't have chance to flush cache. error log message bellow. How can I figure out the reason for server restart? (It wasn't manual restart) I seems

100413 13:42:36 [Note] Event Scheduler: Purging the queue. 0 events
100413 13:42:36 InnoDB: Starting shutdown...
100413 13:42:37 InnoDB: Shutdown completed; log sequence number 0 46419
100413 13:42:37 [Warning] Forcing shutdown of 1 plugins
100413 13:42:37 [Note] C:\MySQL\bin\mysqld.exe: Shutdown complete

100413 13:43:46 InnoDB: Started; log sequence number 0 46419
100413 13:43:46 [Note] Event Scheduler: Loaded 0 events
100413 13:43:46 [Note] C:\MySQL\bin\mysqld.exe: ready for connections.
Version: '5.1.31-enterprise-commercial-pro' socket: '' port: 3306 MySQL Enterprise Server - Pro Edition (Commercial)
100413 16:33:36 [Note] C:\MySQL\bin\mysqld.exe: Normal shutdown

100413 16:33:36 [Note] Event Scheduler: Purging the queue. 0 events
100413 16:33:36 InnoDB: Starting shutdown...
100413 16:33:37 InnoDB: Shutdown completed; log sequence number 0 46419
100413 16:33:37 [Warning] Forcing shutdown of 1 plugins
100413 16:33:37 [Note] C:\MySQL\bin\mysqld.exe: Shutdown complete

100413 16:35:12 InnoDB: Started; log sequence number 0 46419
100413 16:35:13 [Note] Event Scheduler: Loaded 0 events
100413 16:35:13 [Note] C:\MySQL\bin\mysqld.exe: ready for connections.
Version: '5.1.31-enterprise-commercial-pro' socket: '' port: 3306 MySQL Enterprise Server - Pro Edition (Commercial)
100413 17:05:57 InnoDB: Started; log sequence number 0 46419
100413 17:05:58 [Note] Event Scheduler: Loaded 0 events
100413 17:05:58 [Note] C:\MySQL\bin\mysqld.exe: ready for connections.
Version: '5.1.31-enterprise-commercial-pro' socket: '' port: 3306 MySQL Enterprise Server - Pro Edition (Commercial)
100413 22:22:14 [ERROR] C:\MySQL\bin\mysqld.exe: Incorrect key file for table 'YYY.MYI'; try to repair it
100413 22:22:26 [ERROR] C:\MySQL\bin\mysqld.exe: Incorrect key file for table 'XXX.MYI'; try to repair it
100413 22:23:35 [ERROR] C:\MySQL\bin\mysqld.exe: Incorrect key file for table 'XXX.MYI'; try to repair it
100413 22:24:15 [ERROR] C:\MySQL\bin\mysqld.exe: Incorrect key file for table 'XXX.MYI'; try to repair it
100413 22:24:55 [ERROR] C:\MySQL\bin\mysqld.exe: Incorrect key file for table 'XXX.MYI'; try to repair it
100413 22:24:55 [ERROR] C:\MySQL\bin\mysqld.exe: Incorrect key file for table 'XXX.MYI'; try to repair it
100413 22:25:35 [ERROR] C:\MySQL\bin\mysqld.exe: Incorrect key file for table 'XXX.MYI'; try to repair it

Second server didn't shut down or restart at all
=================================================
Error log bellow. Is there any why to realize that is the reason to the table crash? I thought about adding warnings to log, and also setting recover mode, so that MySQL will automatically repair each crashed table. Any other suggestions how to realize the crash reason?

100408 9:58:57 [ERROR] C:\MySQL\bin\mysqld-nt.exe: Table 'XXX' is marked as crashed and should be repaired
100408 9:58:57 [ERROR] C:\MySQL\bin\mysqld-nt.exe: Table 'XXX' is marked as crashed and should be repaired
>>>>>>>>>>> at this point I run repair command, and after 2 days:
100410 11:28:04 [ERROR] C:\MySQL\bin\mysqld-nt.exe: Incorrect key file for table 'MMM.MYI'; try to repair it
100410 11:28:05 [ERROR] Got error 134 when reading table 'MMM'
100410 11:28:06 [ERROR] Got error 134 when reading table 'MMM'
100410 11:28:07 [ERROR] Got error 134 when reading table 'MMM'
100410 11:28:08 [ERROR] Got error 134 when reading table 'MMM'
100410 11:28:09 [ERROR] Got error 134 when reading table 'MMM'
100410 11:28:10 [ERROR] Got error 134 when reading table 'MMM'


Thanks in advance!
Hava



Edited 1 time(s). Last edit at 04/21/2010 04:59AM by Hava Ba.