Bug #26717 InnoDB crashes and unable to recover - Failing assertion
Submitted: 28 Feb 2007 11:51 Modified: 19 May 2007 23:08
Reporter: santhana gopalan Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S1 (Critical)
Version: OS:Windows (Windows)
Assigned to: Assigned Account CPU Architecture:Any

[28 Feb 2007 11:51] santhana gopalan 
Description:
Our MySQL InnoDB got crashed and we could not able to recover. I tried to start with the "innodb_force_recovery = 4" and tried to take tbe dump using mysqldump command. But the MySQL server got crashed when executing the mysqldump. After the analaysis I found that the prolem occured when try to dump of the the table. If I ignored that particular table then the dump works.

My critical data is stored in that particular corrupted table. Due to that I am in very critical position to recover that particular table. I am attching the output with this mail.

Let me know on how to recover it. 

How to repeat:
No.
[28 Feb 2007 11:54] santhana gopalan 
mysql error output

Attachment: mysqldump.txt (text/plain), 13.97 KiB.
[28 Feb 2007 12:30] Heikki Tuuri 
Hi!

Please post the entire .err log from the first crash, if you still have it.

The printout looks like that InnoDB was not able to read the ib_logfiles far enough in crash recovery. Have you deleted the ib_logfiles after the crash?

Regards,

Heikki
[28 Mar 2007 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".
[18 Apr 2007 7:08] santhana gopalan 
The prorblem was due to the .frm file got corrupted. So far I have not faced with the latest Mysql 5.0.37 . The older version created the critical problem to us due to the .frm corruption and due to that the data got lost. Definitely need some type of solution is required when the .frm got corrupted. 

Please let me know on how to recover the data when the .frm file got corrupted in InnoDB?
[19 Apr 2007 23:08] Heikki Tuuri 
Santhana,

the .frm file is a MySQL thing, not InnoDB. Please specify how did it got corrupt, how did you notice that?

Regards,

Heikki
[20 May 2007 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".