Bug #3142 Table corruption with FTS index
Submitted: 11 Mar 2004 8:44 Modified: 23 Mar 2004 10:21
Reporter: Steven Roussey Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Server: MyISAM storage engine Severity:S1 (Critical)
Version:4.1.2 (bk 9 Mar 04) OS:Linux (RHEL 3)
Assigned to: Sergei Golubchik CPU Architecture:Any

[11 Mar 2004 8:44] Steven Roussey
Tables get corrupted when records inserted into them. No error reported in the error log. Only with FTS index.

How to repeat:
I have number of tables that do this and have found some that are small (20MB rather than 20GB) so I can send one. All that needs to be done is to insert each record from the table to a new similar table *one record at a time*. I can send a script in PHP to do this if needed.
[14 Mar 2004 3:56] Alexander Keremidarski
It would be very nice if you can send us one of tables in question.
Upload it at ftp://support.mysql.com/pub/mysql/secret and post name(s) here.
[15 Mar 2004 15:48] Steven Roussey
The data files uploaded (n54_part1.gz,n54_part2.gz, n54_part3.gz, n54_part4.gz) are example data files. I uploaded them without MYI files to save space/bandwidth. You can recreate with REPAIR TABLE ... USE_FRM. I have a script that should hopefully replicate the environment for you that causes the table corruption. It is part 5.
[16 Mar 2004 10:44] Sergei Golubchik
First: I need a .frm file to use REPAIR ... USE_FRM

Second: do I need concatenate ungzipped n54_part[1-4] files to get an original MYD file ? (seems to be the case, but I'd rather ask :)
[16 Mar 2004 13:57] Steven Roussey
No, each gz file is a tar with a .frm and .MYD. Maybe I forgot to choose binary mode for the upload...? I'll try again. The last (small) gz file is a PHP file I thik will repeat the error for you. If not, I can have you run the real program and pull data from our servers over an SSH tunnel or the like. That will take some setup but it will be easy for you to repeat our table corruption. But first, I'll re-upload the files.
[16 Mar 2004 14:16] Steven Roussey
New files:

[16 Mar 2004 14:44] Sergei Golubchik
oops sorry!
Your old files were ok - I didn't notice they were tar archives (they had no tar extension and I didn't try 'file *' on them)

sorry for confusion.
[23 Mar 2004 10:21] Sergei Golubchik
so far I wasn't able to repeat the corruption :(
[23 Mar 2004 15:38] Steven Roussey
OK, email me direct and we'll stream a real example down to you.