Bug #85474 InnoDB: Resetting invalid page type 17855 to 9 when flushing
Submitted: 16 Mar 2017 2:47 Modified: 16 Mar 2017 12:43
Reporter: Desmond Chew Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:5.7.17 OS:Red Hat
Assigned to: CPU Architecture:Any
Tags: resetting invalid page

[16 Mar 2017 2:47] Desmond Chew
Description:
I have the following error found in MySQL error log.

2017-03-15T16:35:23.703678Z 0 [Note] InnoDB: Resetting invalid page [page id: space=0, page number=425984]          type 17855 to 9 when flushing.
2017-03-15T16:35:23.704228Z 0 [Note] InnoDB: Resetting invalid page [page id: space=0, page number=475136]          type 17855 to 9 when flushing.
2017-03-15T16:35:23.704258Z 0 [Note] InnoDB: Resetting invalid page [page id: space=0, page number=49152] t         ype 17855 to 9 when flushing.
2017-03-15T16:35:23.704274Z 0 [Note] InnoDB: Resetting invalid page [page id: space=0, page number=507904]          type 17855 to 9 when flushing.
2017-03-15T16:35:23.704288Z 0 [Note] InnoDB: Resetting invalid page [page id: space=0, page number=65536] t         ype 17855 to 9 when flushing.

How to repeat:
I was running MySQL 5.6.28 with no issue. When I perform an in place upgrade with new binaries 5.7.17, I got the error 

InnoDB: Resetting invalid page [page id: space=0, page number=65536] t         ype 17855 to 9 when flushing

I perform an in place upgrade using 
mysql> mysql_upgrade

Suggested fix:
I am not sure what does it mean when it says resetting invalid page [page idL space=0, page number=xxxx] type 17855 to 9 when flushing.

I found a similar bug that was logged and the solution says was fixed with 5.7.7 
. It might be a different issue.

(Bug #76262)
The fix for this bug is in MySQL 5.7.7. The Release Note will now appear in the 5.7.7 Release Notes document.
[16 Mar 2017 12:43] MySQL Verification Team
Hello Desmond,

Thank you for the report.
Discussed with my senior colleague and concluded that this is not harmful if data files were created in ancient versions of MySQL and later on upgraded.  More details and explanation in Bug #76262(Bug#20691930)

Thanks,
Umesh