MySQL Bugs: #36659: InnoDB: compressed page checksum mismatch

Bug #36659	InnoDB: compressed page checksum mismatch
Submitted:	12 May 2008 4:31	Modified:	28 Nov 2008 13:25
Reporter:	Jui-Nan Lin	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: InnoDB Plugin storage engine	Severity:	S3 (Non-critical)
Version:	1.0	OS:	Linux (Debian 2.6.24-1-amd64)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
I compiled MySQL 5.1.23-rc with InnoDB Plugin 1.0.
After running for 2 or 3 days, MySQL crashes with message: InnoDB: compressed page checksum mismatch. The machine is 2 Intel E5405s and 12 GB RAM. If I run MySQL with MyISAM tables, there is no crash.

Error Log:
080511 23:47:06  InnoDB: compressed page checksum mismatch (space 420 page 17376): 2094689072 != 2684448551
InnoDB: error in sec index entry update in
InnoDB: index `blog_id` of table `pixnet`.`article_hits`
InnoDB: tuple DATA TUPLE: 3 fields;
 0: len 4; hex 8002d289; asc     ;; 1: len 4; hex 80000009; asc     ;; 2: len 4; hex 810a9e48; asc    H;;
 
InnoDB: record PHYSICAL RECORD: n_fields 3; compact format; info bits 0
 0: len 4; hex 00d13f8c; asc   ? ;; 1: len 4; hex 0000000e; asc     ;; 2: len 4; hex 85678000; asc  g  ;;
 
TRANSACTION 19A7026B, ACTIVE 0 sec, process no 19517, OS thread id 1141483856 updating or deleting
mysql tables in use 1, locked 1
2 lock struct(s), heap size 488, 1 row lock(s), undo log entries 1
MySQL thread id 2, query id 298477246 updateINSERT INTO `article_hits` (`aid`, `blog_id`, `status`, `num_reads`) VALUES (17473096, 184969, 2, 2) ON DUPLICATE KEY UPDATE `status` = 2, `num_reads` = `num_reads` + 2
 
InnoDB: Submit a detailed bug report to http://bugs.mysql.com
080511 23:47:06  InnoDB: Assertion failure in thread 1141483856 in file page/page0zip.c line 3923
InnoDB: Failing assertion: slot_rec
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
080511 23:47:06 - mysqld got signal 6;

How to repeat:
Running MySQL with InnoDB for 2 or 3 days.

What does the table definition look like ? 

-sunny

Assigning to Sunny and putting to the Need feedback state.

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

Still needs feedback.

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