MySQL Bugs: #6703: (errno: 145)

Bug #6703	(errno: 145)
Submitted:	18 Nov 2004 18:41	Modified:	18 Nov 2004 20:29
Reporter:	Ozz Nixon	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	4.0.21-nt	OS:	Windows (Windows 2003)
Assigned to:		CPU Architecture:	Any

Description:
<<snippet from my exception log file>>
2004-11-12 16:05:06 Failed to open R1S2Z1C6P43
2004-11-12 16:05:06 [1016] Can't open file: 'r1s2z1c6p43.MYI'. (errno: 145): 
Client:3.23.38
Server:4.0.21-nt

On Nov-11-2004 at 7:41, 13 different MYI files became corrupt on a county wide server. I do not have any more information except I had to rebuild those 13 databases. What causes a 145 error? This is a new release of an existing product that we are testing migration to MySQL over the old embedded SQL db engine. So, I am not sure if I have introduced this error, or maybe the IT staff for this test server.

Thank you,
Ozz

How to repeat:
Not sure what the error means, so I am not sure if this is reproducable.

Suggested fix:
A little more detail of the error would be wonderful!

Not enough information was provide for to process this bug.

Additional Info:

c:\mysql\bin>perror 145
MySQL error:  145 = Table was marked as crashed and should be repaired

Thank you for the bug report.

Just to clarify, "Table was marked as crashed" means corruption was discovered some time ago, and the table was marked corrupted. When you're trying to access such a table you get error 145.
That is this error tell nothing about the nature of corruption - you have to find the first error message about this table - the one when the corruption was discovered for the first time and this "corrupted" flag was set.