Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.12, 10.3.10, 10.1.37
-
None
Description
See the following error message:
2018-11-05 3:53:42 139986889774848 [ERROR] InnoDB: Page 227027:2591 may be corrupted. Post encryption checksum 3926119398 stored [3479160576:3479160576] key_version 1
|
2018-11-05 03:53:42 0x7f513cd69700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/storage/innobase/rem/rem0rec.cc line 580
|
This is printed here:
A lot of people seem to think that 227027 in the above message would refer to the page number, but it actually refers to the tablespace ID. I think we should improve this message. Maybe something like?:
2018-11-05 3:53:42 139986889774848 [ERROR] InnoDB: Page in tablespace 227027 with offset 2591 may be corrupted. Post encryption checksum 3926119398 stored [3479160576:3479160576] key_version 1
|
2018-11-05 03:53:42 0x7f513cd69700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/storage/innobase/rem/rem0rec.cc line 580
|
Attachments
Issue Links
- relates to
-
MDEV-11939 innochecksum mistakes a file for an encrypted one (page 0 invalid)
- Closed
-
MDEV-12112 corruption in encrypted table may be overlooked
- Closed
-
MDEV-13542 Crashing on a corrupted page is unhelpful
- Closed
-
MDEV-17957 Make Innodb_checksum_algorithm stricter for strict_* values
- Closed
-
MDEV-17958 Make bug-endian innodb_checksum_algorithm=crc32 optional
- Closed
-
MDEV-18025 Mariabackup fails to detect corrupted page_compressed=1 tables
- Closed
-
MDEV-18529 InnoDB wrongly skips decryption of encrypted page if unencrypted and post-encrypted checksums match
- Closed