MySQL Bugs: #65579: InnoDB: Page dump in ascii and hex

Bug #65579	InnoDB: Page dump in ascii and hex - filled drive in minutes
Submitted:	11 Jun 2012 7:07	Modified:	11 Jun 2012 15:04
Reporter:	jj jj	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S2 (Serious)
Version:	5.5.24	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
I don't know why error did occur in a first place but when it did it did ssd drive in minutes writing over and over again some dumps to logfile! If it were normal harddrive then it would probably overload it tottaly. Option to trim/turn off those innodb page dumps please :(

120611 5:53:10 InnoDB: Page checksum 754939127, prior-to-4.0.14-form checksum 79124242
InnoDB: stored checksum 4273537243, prior-to-4.0.14-form stored checksum 79124242
InnoDB: Page lsn 33 268745319, low 4 bytes of lsn at page end 268745319
InnoDB: Page number (if stored to page already) 10,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 252323
InnoDB: Page may be an index page where index id is 481260
InnoDB: (index "PRIMARY" of table "seo_piwvkn"."piwikvkn_archive_blob_2011_07")
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 10.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 10.
InnoDB: You may have to recover from a backup.
120611 5:53:10 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex feb900db0000000a000000090000000d000000211004ba674..... A LOT OF DATA HERE
InnoDB: End of page dump

How to repeat:
....

Please, check if adding

innodb_force_load_corrupted=1

to my.cnf and restart helps in any way.

Looks like here we have a feature request for option to NOT output page dumps in case of corruption. Please, confirm.

Can you provide more information about your HW configuration ?

HW model / vendor
Disk controller

file system and mount options

I don't want innodb to load anything corruped and YES option is needed to mysql NOT dump such amount of data to a logfile. It filled drive in minutes and causes other server aplication to halt/crash that are using that drive... I don't think this should be default behavior, dumping same data over and over and over, filing and overloading drive.

I agree with this as a reasonable (new) feature/option request. 

If you think that root cause of this corruption is related to some MySQL bug/fault, please, feel free to open new bug report and provide additional information about hardware requested by Arnaud there.

Duplicate of Bug#65469