MySQL Bugs: #36884: innodb corruption

Bug #36884	innodb corruption
Submitted:	22 May 2008 11:23	Modified:	12 Dec 2009 22:57
Reporter:	Tordjman Yohan	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S1 (Critical)
Version:	5.0.51a	OS:	Linux (64bits / 32bits)
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	innodb corruption crash

Description:
I created yesterday a new database and table in innodb (in Zimbra)...

Without any problem of the computer, a table start to be corrupted and crash the server.... 

i tryied to check and to recover that, but the server always crash
( i used the innodb_force_recovery param too, to do a dump, but *nothing* )

I can send all the files, crash dump... etc...

How to repeat:
don't know !

Suggested fix:
don't know !

error log

Attachment: error.bz2 (application/octet-stream, text), 67.26 KiB.

I checked all the databases, and have the same kind of bug in 32bits systems.

my systems are based on ubuntu gutsy.

accessing to a table crash the server...

in 32bits the "innodb crash recovery" repair correctly the table.
mysqlcheck does not report another problem on it...

InnoDB: Error: page n:o stored in the page read in is 1668240719, should be 43!
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 43.
...
080522  1:31:45  InnoDB: Page checksum 1399919813, prior-to-4.0.14-form checksum 717545827
InnoDB: stored checksum 2001433387, prior-to-4.0.14-form stored checksum 1781488178
InnoDB: Page lsn 912488056 1131957618, low 4 bytes of lsn at page end 796345157
InnoDB: Page number (if stored to page already) 1668240719,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 1800557134
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 43.

The entire page looks like garbage! Also page contents look like random bytes. I have never seen such corruption report prior to this.

Did you move ibdata files around or compress or encrypt them?

Does your computer's disk drive work ok? RAM is ok?

Regards,

Heikki

> Did you move ibdata files around or compress or encrypt them?

No, nothing like that... 

> Does your computer's disk drive work ok? RAM is ok?

Yes, all ok, no other crash...
This kind of bug appears randomly on my innodb databases...

Are you still experiencing the issue and tried a new server version?. Thanks in advance.

Hi, 
 since that, i have upgraded the servers from gutsy to hardy, new kernel version, and up to 5.0.67...

I have many times less corruption reporting
(maybe gutsy ? some people says that gutsy was not good...)

Have you upgraded and experiencing the same issue?. Thanks in advance.

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