Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-17638

Improve error message about corruption of encrypted page

    Details

      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:

      https://github.com/MariaDB/server/blob/5567a8c936ede50efcdf4a7f898dbaa058106d70/storage/innobase/fil/fil0crypt.cc#L2639

      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

            Activity

              People

              • Assignee:
                kevg Eugene Kosov
                Reporter:
                GeoffMontee Geoff Montee
              • Votes:
                2 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: