Hello.
I suggest you to use 4.1.10 (in 4.1.8 was fixed a bug #6784, I haven't seen it in a changelist of 4.0.x branch). If myisamchk -r *.MYI, myisamchk -o *.MYI doesn't solve the problem, as the last chance, use USE_FRM mode of REPAIR command. But you may lose some information about the table's metadata, make a backup. See: http://dev.mysql.com/doc/mysql/en/repair-table.html "Steven Roussey" <[EMAIL PROTECTED]> wrote: >> See: >> http://downloads.mysql.com/archives.php > > Thank you. Nice link to have around. > >>> Key 3 is the FTS key. The others are a UNIQUE KEY (#1) and a KEY(#2). >> >>Do you have the same values for full-text parameters (ft_mit_word_len >>for example)? > > Not at first. I had noticed that not long after I sent my message, and I > rebuilt all the tables with "mysamchk -rf *MYI". That eliminated the > Duplicate Key errors, but not the "Incorrect key file... Try to repair it" > error. > > Did it again with 4.0.18 and had the same error. :( > > Next I did "mysamchk -o *MYI" to really be sure, and I even used the 4.0.18 > binary. Then I tried running 4.0.23 with debug turned on (somewhat) and > still get the error. I'll try again with 4.0.18 (or 17) with debug and see > if it has the same error at the same place. > > Here is what I had in the trace file (note that the query is a replace cmd > that often is used to update an entry): Do I need more fine grain debug info > to find the error? > > > mysql_change_db: info: Use database: search > do_command: info: Command on TCP/IP (9) = 3 (Query) > dispatch_command: query: replace into forums_posts_1239959 > (forumid,messageid,parent,rootmessageid,deleted,deleted_marked,approved,auto > respond,loginid,ip,user_id,author,email,title,message,search_forumid ) > values > (2255626,1108700026,0,1108700026,'no','no','yes','no',1524436,1100232325,'1c > c48d0a485629a91e2b5634c122a339', > '[EMAIL PROTECTED]','[EMAIL PROTECTED]','Message text deleted for > privacy, but I can sent if needed','fid2255626') > thr_lock: info: write_wait.data: 0x0 > mi_get_status: info: key_file: 28418048 data_file: 39236852 > mi_write: error: Got error: 121 on write > _mi_writeinfo: info: operation: 1 tot_locks: 1 > _mi_ck_delete: info: root_page: 19973120 > _mi_prefix_search: info: key: '004' > _mi_prefix_search: info: key: '004' > _mi_prefix_search: info: key: '004' > _mi_prefix_search: info: key: '004' > d_search: error: Didn't find key > mi_update: error: key: 2 errno: 126 > _mi_writeinfo: info: operation: 1 tot_locks: 1 > my_message_sql: error: Message: 'Incorrect key file for table: > 'forums_posts_1239959'. Try to repair it' > thr_unlock: info: updating status: key_file: 28418048 data_file: 39236852 > mi_lock_database: info: changed: 1 w_locks: 0 > > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
