| Bug #81429 | innochecksum rises an error with encryption enabled table at page 1 | ||
|---|---|---|---|
| Submitted: | 16 May 2016 8:53 | Modified: | 16 May 2016 9:04 |
| Reporter: | Shahriyar Rzayev | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Command-line Clients | Severity: | S1 (Critical) |
| Version: | 5.7.12 | OS: | CentOS (7) |
| Assigned to: | CPU Architecture: | Any | |
[16 May 2016 9:04]
MySQL Verification Team
Hello Shahriyar, Thank you for the report. Thanks, Umesh
Description: Here is the test: mysql> show create table sbtest1\G *************************** 1. row *************************** Table: sbtest1 Create Table: CREATE TABLE `sbtest1` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `k` int(10) unsigned NOT NULL DEFAULT '0', `c` char(120) NOT NULL DEFAULT '', `pad` char(60) NOT NULL DEFAULT '', PRIMARY KEY (`id`), KEY `k_1` (`k`) ) ENGINE=InnoDB AUTO_INCREMENT=2001 DEFAULT CHARSET=latin1 MAX_ROWS=1000000 ENCRYPTION='Y' 1 row in set (0.00 sec) [root@mysql-57 ~]# systemctl stop mysqld.service [root@mysql-57 ~]# innochecksum /var/lib/mysql/dbtest/sbtest1.ibd Fail: page 1 invalid Exceeded the maximum allowed checksum mismatch count::0 How to repeat: See description Suggested fix: It seems to be the page 1 is really corrupted or innochecksum does not aware of encryption pages.