Bug #79725 Check algorithm=innodb on crc32 checksum mismatch before crc32(big endian) (cont
Submitted: 21 Dec 2015 22:28 Modified: 19 Jan 2016 13:16
Reporter: OCA Admin (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:5.7 OS:Any
Assigned to: CPU Architecture:Any

[21 Dec 2015 22:28] OCA Admin
Description:
This bug tracks a contribution by Daniel Black (Github user: grooverdan) as described in http://github.com/mysql/mysql-server/pull/39

How to repeat:
See description

Suggested fix:
See contribution code attached
[21 Dec 2015 22:28] OCA Admin
Contribution submitted via Github - Check algorithm=innodb on crc32 checksum mismatch before crc32(big endian) 
(*) Contribution by Daniel Black (Github grooverdan, mysql-server/pull/39#issuecomment-166430694): I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

Contribution: git_patch_54220060.txt (text/plain), 1.38 KiB.

[22 Dec 2015 4:27] Umesh Shastry
Hello!

Thank you for the report and contribution.

Thanks,
Umesh
[19 Jan 2016 13:16] Daniel Price
Posted by developer:
 
Fixed as of the upcoming 5.7.12, 5.8.0 release, and here's the changelog entry:

InnoDB attempted crc32 checksum validation instead of innodb after a
crc32 checksum validation failure, causing repeated crc32 checksum
validation attempts. Checksum validation order is now optimized
dynamically. 

Thanks to Daniel Black for the patch.