Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.1.21
-
Debian Wheezy amd64
-
10.1.22, 10.2.6-2, 10.2.6-3
Description
innochecksum returns an error message when ran on ibdata1 on a server that is working fine (a check on all tables has been done without finding anything) :
# innochecksum -d /var/lib/mysql/ibdata1
|
InnoDB offline file checksum utility.
|
|
Variables (--variable-name=value)
|
and boolean options {FALSE|TRUE} Value (after reading options)
|
--------------------------------- ----------------------------------------
|
verbose TRUE
|
debug TRUE
|
skip-corrupt FALSE
|
count FALSE
|
start-page 0
|
end-page 0
|
page 0
|
per-page-details FALSE
|
leaf FALSE
|
merge 0
|
Table is uncompressed
|
Page size is 16384
|
file /var/lib/mysql/ibdata1 = 3844079616 bytes (234624 pages)...
|
InnoChecksum; checking pages in range 0 to 234623
|
Page 0 encrypted key_version 5 checksum 1135705172
|
page 0: log sequence number: first = 1136557346; second = 1136557346
|
page 0: old style: calculated = 2609070081; recorded = 2609070081
|
page 0: new style: calculated = 3631443077; crc32 = 286255075; recorded = 1135705172
|
Fail; page 0 invalid (fails innodb and crc32 checksum)
|
This server was previously running on 10.0 and was just upgraded to 10.1 and it is not using tablespace encryption.
Attachments
Issue Links
- blocks
-
MDEV-13443 Port innochecksum tests from 10.2 innodb_zip suite to 10.1
- Closed
- causes
-
MDEV-20583 innochecksum man pages seem to be inconsistent with the binary (10.2.25)
- Closed
- includes
-
MDEV-13279 innodb_zip.innochecksum_3 failed in buildbot (InnoDB warnings)
- Closed
- relates to
-
MDEV-11759 Encryption code in MariaDB 10.1/10.2 causes compatibility problems
- Closed
-
MDEV-12711 backup may show corruption with custom innodb_data_file_path
- Closed
-
MDEV-17638 Improve error message about corruption of encrypted page
- Closed
-
MDEV-18529 InnoDB wrongly skips decryption of encrypted page if unencrypted and post-encrypted checksums match
- Closed