Bug #8399 delete and insert with large amount of data crashes index table with error 1034

• Submitted: 9 Feb 2005 21:02
• Modified: 9 Feb 2005 21:20
• Reporter: [ name withheld ]
• Status: Can't repeat
• Category: MySQL Server: MyISAM storage engine
• Severity: S1 (Critical)
• Version: 4.1.9
• OS: Windows (Win2k3)
• CPU Architecture: Any

[9 Feb 2005 21:02] [ name withheld ]

Description:
I am running an OLAP application where logfiles are aggregated from log-tables into result tables using count and group by. The proces first uses  'delete' to remove all lines from a certain month out of the result table an then an insert statement to insert new aggregated data. on an average about 150.000 lines are deleted and inserted into the result table.
About every two or three days the index of the result table crashes with a 1034 error code. The table can be repaired with myisamchk but it disturbes the automated process and can only be done by hand. I am using the same server hardware since 4.0.13 but i only get these errors since upgrading to 4.1.9.
The myisamchk log reads like this:

Checking MyISAM file: y:\annatool\auswertung_04.myi
Data records:  575313   Deleted blocks:  121180
myisamchk: warning: Table is marked as crashed
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
myisamchk: error: Found 574949 keys of 575313
- check record links
myisamchk: error: Keypointers and record positions doesn't match
MyISAM-table 'y:\annatool\auswertung_04.myi' is corrupted
Fix it using switch "-r" or "-o"

How to repeat:
I don't really know. It sound like the bug reported in #3308

[9 Feb 2005 21:20] MySQL Verification Team

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.