MySQL Bugs: #63903: InnoDB: Page directory corruption

Bug #63903	InnoDB: Page directory corruption
Submitted:	2 Jan 2012 21:21	Modified:	14 Feb 2012 10:17
Reporter:	Lars Ehrhardt	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Errors	Severity:	S3 (Non-critical)
Version:	5.1.41	OS:	Linux (Ubuntu 10.04)
Assigned to:		CPU Architecture:	Any

Description:
Since a week our mysql server is crashing once a day during the morning. We first thought that there might be a problem with the underlying hardware - but this is a virtual instance and just to be sure we have migrated this instance to a different machine. Problem is still the same. The problem seems to be hard to trigger on purpose - one day mysql was constantly crashing and restarting and we could only fix it with a cold shutdown of the instance. After this restart everything was fine again. Dumping all databases triggers a crash sometimes but other times this works without a problem.

The machine has 4 GB RAM, 4 cpu cores and is a 32bit ubuntu instance.

How to repeat:
Run mysql for 24hours and wait for the log messages.

error log

Attachment: mysql.log (text/x-log), 15.35 KiB.

Your server version is quite older, please test the version 5.1.60. Thanks.

Since Ubuntu 10.04 LTS is a long time service version we would rather stick to this version or can you confirm, that this is a known bug with version 5.1.41 which is fixed by a later version?

Thank you for the feedback.

Well, I see at least one bug which can affect your case: bug #59465. You have crashes at btr_estimate_number_of_different_key_vals. And there were a lot of bugs with crashes in dict_update_statistics.

Also we don't fix bugs in old versions, don't backport bug fixes, so need to check with latest version anyway. So, please, upgrade and inform us if problem still exists.

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".