I already wrote about this issue but as I is third team I'm helping customers to resolve this "frm corruption" issue it is the time to return to it again.
During MySQL 5.0 release cycle the change was made so now MySQL does not stop if Innodb storage engine failed to initialize but starts properly... just having Innodb tables unavailable. I honestly do not know any case when this behavior change helps... of course you silently want to get good portion of your database unavailable right ? But I guess this change was made for reasons quite far from improving user experience.
It is worth to note MySQL 5.0 introduces STRICT option which will makes error control more strict, what is often expected by the Enterprise users - so instead of cutting the string lengths or converging NULLs to zeros MySQL can be tuned to abort such …
[Read more]