Bug #72645 INNODB SHOULD ABORT WHEN A PAGE IN SYSTEM, UNDO OR TEMP TABLESPACE IS CORRUPTTED
Submitted: 14 May 2014 9:37 Modified: 24 Oct 2014 6:58
Reporter: Shaohua Wang Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:5.7 OS:Any
Assigned to: CPU Architecture:Any

[14 May 2014 9:37] Shaohua Wang 
Description:
In buf0buf.cc:buf_page_io_complete

/* If page space id is larger than TRX_SYS_SPACE
(0), we will attempt to mark the corresponding
table as corrupted instead of crashing server */
if (bpage->id.space() > TRX_SYS_SPACE
    && buf_mark_space_corrupt(bpage)) {
        return(false);
} else {
        ib_logf(IB_LOG_LEVEL_FATAL,
                "Aborting because of a"
                " corrupt database page.");
} 

How to repeat:
As Description.

Suggested fix:
1. we should abort not only for system tablespace, but for undo tablespace, and temp tablespace.
2. print error message like "corrupt database page in the system tablespace'%s'"
[14 May 2014 10:09] MySQL Verification Team 
Hello Shaohua,

Thank you for the bug report.

Thanks,
Umesh
[24 Oct 2014 6:58] Marko Mäkelä 
This is a duplicate of
Bug#10132 Crashing the server on corrupt InnoDB page is unhelpful