Bug #47357 | Mysql crashes when repairing ARCHIVE table | ||
---|---|---|---|
Submitted: | 16 Sep 2009 9:05 | Modified: | 22 Oct 2009 7:26 |
Reporter: | Davide Ferrari | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Archive storage engine | Severity: | S1 (Critical) |
Version: | 5.1.36 | OS: | Linux |
Assigned to: | CPU Architecture: | Any |
[16 Sep 2009 9:05]
Davide Ferrari
[16 Sep 2009 9:41]
Valeriy Kravchuk
Thank you for the problem report. Can you try to identify the exact table for which REPAIR crashed?
[18 Sep 2009 9:17]
Davide Ferrari
I've have possibly one table but I cannot do anything on this table, not even a show create cause it says: ERROR 1034 (HY000): Incorrect key file for table 'API_log_requests_090815'; try to repair it and if I try to repair it repair table NO_ENTRAR_hist_datalogs.API_log_requests_090815; +-------------------------------------------------+--------+----------+----------+ | Table | Op | Msg_type | Msg_text | +-------------------------------------------------+--------+----------+----------+ | NO_ENTRAR_hist_datalogs.API_log_requests_090815 | repair | error | Corrupt | +-------------------------------------------------+--------+----------+----------+ 1 row in set (0.00 sec)
[18 Sep 2009 11:20]
Susanne Ebrecht
Did you upgrade from 5.0 or an older 5.1 version?
[18 Sep 2009 11:21]
Davide Ferrari
No, they are backup tables generated from InnoDB ones on the same server (with an ALTER TABLE statement)
[21 Sep 2009 8:16]
Sveta Smirnova
Thank you for the feedback. Could you please upload files API_log_requests_090815.ARZ, API_log_requests_090815.ARM and API_log_requests_090815.frm to our FTP server as described in "Files" section?
[21 Sep 2009 8:40]
Davide Ferrari
Requested table files uploaded to Mysql's FTP
[21 Sep 2009 9:47]
Sveta Smirnova
Thank you for the feedback. When I try to repair table provided I get not error. But if I convert it to InnoDB, then to Archive I get error "ERROR 1022 (23000): Can't write; duplicate key in table '#sql-73d9_1'" How did you converted InnoDB table to Archive?
[21 Sep 2009 11:04]
Davide Ferrari
Ok, sorry for that, this actually was an OK table, I made a little of confusion cause I dropped many corrupted tables trying to get the server running smoothly. I've just uploaded another table, this time is 100% corrupt and REPAIR doesn't repair it. I don't know if it's exactly this table that made the server crash but anyway something went wrong with this and other tables, so if you could take a look at it... TIA
[21 Sep 2009 18:38]
MySQL Verification Team
What is the file name you have uploaded?. Thanks in advance.
[22 Sep 2009 7:26]
Sveta Smirnova
Thank you for the feedback. I still can not repeat crash. Additionally version 5.1.36 is old. Please try with current version 5.1.39 and if problem still exists indicate accurate name of MySQL package you are using (file name downloaded) and provide your configuration file.
[22 Oct 2009 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".