Bug #68412 Corrupted databases after upgrade from 5.1 to 5.5
Submitted: 18 Feb 2013 1:19 Modified: 24 Mar 2015 18:47
Reporter: jjj h Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Server: InnoDB storage engine Severity:S2 (Serious)
Version:5.5 OS:Linux
Assigned to: CPU Architecture:Any

[18 Feb 2013 1:19] jjj h
After upgrade from 5.1 to 5.5, three tables in three databases (all with the same structure) ends up corrupted:
 - When i try to drop these tables, MySQL says they don't exists
 - When i try to create table with the same name, MySQL says it already exists
 - When i try to drop database, MySQL crashes

How to repeat:
Really don't know.
[18 Feb 2013 1:19] jjj h
crash log

Attachment: syslog (application/octet-stream, text), 8.33 KiB.

[18 Feb 2013 5:57] MySQL Verification Team

Can you show us full mysql error logs from before the upgrade up until now? Did you use innodb plugin or builtin innodb in 5.1?  Did you perform a "slow shutdown" before upgrading? (set global innodb_fast_shutdown=0) ?
[18 Feb 2013 8:09] jjj h
i'm not setting 'innodb_fast_shutdown' in config file so default value is used:

mysql> show variables like 'innodb_fast_shutdown';
| Variable_name        | Value |
| innodb_fast_shutdown | 1     |

I don't know if i had plugin or buildin innodb, i just used packages from Debian Squeeze.
[18 Feb 2013 8:14] MySQL Verification Team
It looks like DROP DATABASE is causing a crash due to missing tables (see end of syslog2.log for their names).

Probably same issue reported as:
and internal ( bug not yet fixed ):

[18 Feb 2013 9:37] jjj h
Ok, any ideas how can i remove these corrupted databases so i can recreate them from backup? thank you
[19 Feb 2013 18:42] Sveta Smirnova
Please try suggestions from http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
[22 Feb 2013 3:51] jjj h
I already tried everything but nothing helps.
[14 Mar 2013 7:23] jjj h
No fix for this??
[24 Feb 2015 18:47] Sveta Smirnova
HI jjj,

bug #65845 has been fixed in versions 5.6.12 and 5.7.2. Please upgrade to 5.6 or 5.7 branch, try with it and inform if this bug still exists.
[25 Mar 2015 1: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".