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: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 4.0.21-nt | OS: | Windows (Windows 2003) |
Assigned to: | CPU Architecture: | Any |
[18 Nov 2004 18:41]
Ozz Nixon
[18 Nov 2004 18:57]
MySQL Verification Team
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.
[18 Nov 2004 20:29]
Sergei Golubchik
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.