Bug #67471 InnoDB redundancy in system TS
Submitted: 5 Nov 2012 9:21 Modified: 27 Feb 2013 9:18
Reporter: Oli Sennhauser Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S4 (Feature request)
Version:all OS:Any
Assigned to: CPU Architecture:Any

[5 Nov 2012 9:21] Oli Sennhauser 
Description:
We see more and more often MySQL used on virtualized systems (VMware). From time to time VMware crashes at customers and leaves a corrupted InnoDB system tablespace behind.
If the InnoDB DD is concerned by such corruptions it is hard to even start the database or read the meta information for accessing the data.

How to repeat:
Run traffic on InnoDB tables and crash VMware

Suggested fix:
I was thinking about if it would make sense to have all or at least the most important meta data information of innodb somewhere in the system tablespace redundant for such situations as it is done in some file systems for example.

And yes, I know it would make more sense to have a proper backup!
[27 Feb 2013 9:18] MySQL Verification Team 
Shall we just say this is a FR for whatever new data dictionary implementation might come into existence sometime in the future.