Bug #22384 | DELETE FROM table causes "Incorrect key file for table" | ||
---|---|---|---|
Submitted: | 15 Sep 2006 9:42 | Modified: | 10 Oct 2006 18:33 |
Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: MyISAM storage engine | Severity: | S1 (Critical) |
Version: | 4.0BK,4.1BK,5.0BK,5.1BK | OS: | Any (*) |
Assigned to: | Ingo Strüwing | CPU Architecture: | Any |
Tags: | corruption, crash, keyfile, myisam, table |
If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.
To split a large file:
- On *nix platforms use the split command e.g.
split -b 50MB <my_large_archive> <my_split_archive_prefix>
- On windows use WinZip or a similar utility to split the large file
[16 Sep 2006 23:11]
Shane Bester
[17 Sep 2006 8:22]
Shane Bester
ANOTHER TESTCASE that can show key file crash when imported.
Attachment: bug22384_testcase2.zip (application/zip, text), 148.65 KiB.
[17 Sep 2006 10:34]
Shane Bester
Yes another slightly different testcase. import into mysql
Attachment: bug22384_testcase3.zip (application/zip, text), 190.85 KiB.
[28 Sep 2006 9:21]
Ingo Strüwing
My test case which seems too big for the test suite.
Attachment: bug22384.test.gz (application/x-tar, text), 148.63 KiB.
[29 Sep 2006 10:07]
Shane Bester
smallest testcase I can come up with on 5.0
Attachment: t1_120859_ark.zip (application/x-zip-compressed, text), 106.58 KiB.