Bug #81859 | On win64 the checksums in buf_page_print can be wrong (e.g. none 8030895855 ) | ||
---|---|---|---|
Submitted: | 15 Jun 2016 10:14 | ||
Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 5.6.31 | OS: | Windows (x64) |
Assigned to: | CPU Architecture: | Any |
[15 Jun 2016 10:14]
Shane Bester
[15 Jun 2016 10:15]
MySQL Verification Team
I'm referring to the output when a corruption is found. e.g. InnoDB: uncompressed page, stored checksum in field1 769419609, calculated checksums for field1: crc32 769419609, innodb 3903488443, none 3735928559, stored checksum in field2 769419609, calculated checksums for field2: crc32 769419609, innodb 3718464063, none 8030895855, page LSN 47 1057076440, low 4 bytes of LSN at page end 1057076440, page number (if stored to page already) 25373, space id (if created with >= MySQL-4.1.1 and stored already) 1931