Bug #1398 Can't open file: 'example.MYI'. (errno: 145)
Submitted: 25 Sep 2003 3:53 Modified: 3 Feb 2011 17:27
Reporter: Tom Sommer Email Updates:
Status: Not a Bug Impact on me:
Category:MySQL Server: MyISAM storage engine Severity:S1 (Critical)
Version:4.0.15 Binary&Source OS:Linux (Linux Redhat)
Assigned to: CPU Architecture:Any

[25 Sep 2003 3:53] Tom Sommer
Some of our customers are experiancing problems after we upgraded our mySQL servers to MySQL 4.0.15

They are at random intervals receiving this error: Can't open file: 'example.MYI'. (errno: 145)

When we move them to a MySQL 3 server, they have no problems.

We first used the source tarball but switched to the binary version to see if that could resolve our problem, but it did not.

The problem only occurs on a few number of customers, compared to the total number. But the situation is still unacceptable

How to repeat:

Suggested fix:
You can repair the damaged table, but the problem WILL reoccur again
[25 Sep 2003 4:05] Tom Sommer
I should note we used version 3.23.54a prior to upgrading

And also that this error also occurred in 4.0.14
[25 Sep 2003 11:50] Indrek Siitan
How often does this occur? It would be great, if you could provide us with
a repeatable test case. To do this, can you follow these steps next time
the corruption occurs:

 1. Shut down the MySQL server
 2. Take a copy of the 3 table files of the corrupted table
 3. Fix the table with myisamchk
 4. Add "log-bin" and "log-isam" into your /etc/my.cnf [mysqld] section.
 5. Start the server.

Now, if the corruption happens again, send us the following:
 * the corrupted table files from the first corruption
 * binary and MyISAM log generated since first corruption
 * corrupted table files from the second corruption
[14 Feb 2005 22:54] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[1 Sep 2006 10:34] dimitri hilverda
I got this same error after upgrading on a linux RH enterprice server.

is there a fix for this?

My supportdesk tels me that this is the only version that works with plesk.

Is there a way to rollback to the old version?
[29 Jan 2011 19:10] Rahul Rajpal
There is an easier way to repair the corrupted tables and recover data from them. To do so, the administrator needs to go on this link:
[3 Feb 2011 17:27] Valeriy Kravchuk
While recent comment is useful, I still see nothing in this report about real bug in any of currently supported MySQL server version.