Bug #55388 MySQL Server crashes cause InnoDB database corruption

• Submitted: 20 Jul 2010 8:21
• Modified: 23 Aug 2010 14:01
• Reporter: Anton Chernomazov
• Status: No Feedback
• Category: MySQL Server: Windows
• Severity: S2 (Serious)
• Version: 5.1.48
• OS: Windows (Server 2008 SP2 Core)
• CPU Architecture: Any

[20 Jul 2010 8:21] Anton Chernomazov

Description:
MySQL server stands on VMWare ESXi virtual machine. Host was powered off cause electricity problem. After this MySQL server crashes on start.
I upgrade MySQL server from 5.1.44 to 5.1.48, but nothing has changed.
I try innodb_force_recovery parameter with values 5 and 6. Log messages was changed, but server still crashes.
I try to remove InnoDB log files, server recreate it, but still crashes.

How to repeat:
I have no instruction how to repeat this situation.

[20 Jul 2010 8:21] Anton Chernomazov

Error log with backtrace

Attachment: mysql.err (application/octet-stream, text), 13.90 KiB.

[20 Jul 2010 8:45] Sveta Smirnova

Thank you for the report.

This can be bug in recovery. Could you please send us ib* files compressed and your configuration file?

[20 Jul 2010 14:35] Anton Chernomazov

I place file bug-data-55388.7z in ftp://ftp.mysql.com/pub/mysql/upload/.

[20 Jul 2010 18:30] MySQL Verification Team

Please provide the my.ini file too. Thanks.

[21 Jul 2010 4:27] Anton Chernomazov

my.ini file

Attachment: my.ini (application/octet-stream, text), 8.91 KiB.

[23 Jul 2010 10:28] Sveta Smirnova

Thank you for the file.

> I try innodb_force_recovery parameter with values 5 and 6. Log messages was changed, but
server still crashes.
> I try to remove InnoDB log files, server recreate it, but still crashes.

I can not repeat crash with innodb_force_recovery set to 5. So this is not a bug from this point of view.

But as you wrote server still crashes with different message could you please send us this message with innodb_force_recovery=5 or 6?

[23 Jul 2010 12:14] Anton Chernomazov

Early attached mysql.err file includes messages for innodb_force_recovery 5 and 6. 
It's very strange, but i cannot repeat crash with innodb_force_recovery = 5 on the original ibdata1 file.

[23 Jul 2010 12:18] Anton Chernomazov

When i try to delete all tables from `kav` database, server crashes with following messages.

Attachment: mysql.err (application/octet-stream, text), 5.49 KiB.

[23 Jul 2010 14:01] Sveta Smirnova

Thank you for the feedback.

Does server crash when you use innodb_force_recovery=6 option? If yes, please send us *frm files from kav database.

[23 Aug 2010 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".