MySQL Bugs: #68464: Ending processing because of a corrupt database page

Bug #68464	Ending processing because of a corrupt database page
Submitted:	22 Feb 2013 17:57	Modified:	22 Mar 2013 18:49
Reporter:	Dave Kelsey	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S2 (Serious)
Version:	5.5.28 64	OS:	Solaris (joyent_20120126T071347Z i86pc i386 i86pc Solaris)
Assigned to:		CPU Architecture:	Any
Tags:	innodb, page

Description:
Forced to move to new hardware, our prod DB has operated without any issues for 2 months( 4 years before that).
no changes have been made, same usage patters etc.

this week: tues 2AM the server crashed 

"InnoDB: Database page corruption on disk or a failedInnoDB: file read of page 767636.InnoDB: You may have to recover from a backup."

I put the DB in recovery mode, dumped with mysqldump, rebuild the DB, (shut it down, delete all ib_data? and ibdata files and loaded from the backup)

Wednesday arount 2AM again the server crashed.

InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 767636.
InnoDB: You may have to recover from a backup.

I suspect it is a hardware driver or disc cache.  I'll attache the error.log which contains dumps of the pages as well as stack traces.

How to repeat:
I don't know what triggers it.  It seems to occur around the same time in the early morning.
I don't think there are any crontabs that correspond to when it happens.

Thank you for the report.

Have you checked disk and /var/log/messages for errors? If not, please do it now.

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