MySQL Bugs: #63342: Corrupted myisam table

Bug #63342	Corrupted myisam table
Submitted:	20 Nov 2011 16:21	Modified:	29 Nov 2011 21:21
Reporter:	Jamie Koc	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: General	Severity:	S1 (Critical)
Version:	5.1.42	OS:	Linux
Assigned to:		CPU Architecture:	Any

Description:
Wrong bytesec: 0-0-0 at linkstart: 40961652

How to repeat:
Not sure how to repeat. The issue has occurred three times in the last week.

Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

How do I obtain more information as to what is causing the table corruption?
Is there any error logging I can turn on?

We have a process that inserts millions of records into this table.
However, I can not tell at what point the table corruption occurs.

Do you need information about the table itself?

Thanks

First of all we need to know if the problem is repeatable with current version, 5.1.59+. Then indeed, complete CREATE TABLE and typical INSERT statement would be useful, as well as my.cnf from your server. Also check, please, of there are any suspicious messages in the error log.

To summarize: we need to know what exact steps to perform on recent server version, outside of your environment, to get the same corruption.

Closing out this issue. We noticed that lowering the myisam sort buffer from 4G -> 3G resolved the corruption issue. I also saw table corruption when using optimize table. The indexes got completely destroyed.