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

Encryption bogus message still in 10.1.5

    XMLWordPrintable

Details

    • 10.1.6-1

    Description

      2015-06-10 13:47:03 140177671497760 [Note] /usr/sbin/mysqld (mysqld 10.1.5-MariaDB-log) starting as process 60572 ...
      [...]
      2015-06-10 13:47:12 140177671497760 [Warning] InnoDB: Found potentially bogus bytes on page 0 offset 10428 for space 2977 : [ 80 00 00 3d 80 b1 ]. Assuming space is not encrypted!.
      2015-06-10 13:47:12 140177671497760 [Warning] InnoDB: Found potentially bogus bytes on page 0 offset 10428 for space 2978 : [ 00 0e 80 00 00 16 ]. Assuming space is not encrypted!.
      2015-06-10 13:47:12 140177671497760 [Warning] InnoDB: Found potentially bogus bytes on page 0 offset 10428 for space 2980 : [ 00 0e 80 b5 0e 39 ]. Assuming space is not encrypted!.
      2015-06-10 13:47:14 140177671497760 [Warning] InnoDB: Found potentially bogus bytes on page 0 offset 10428 for space 2343 : [ 00 2f 02 58 21 65 ]. Assuming space is not encrypted!.
      2015-06-10 13:47:15 140177671497760 [Warning] InnoDB: Found potentially bogus bytes on page 0 offset 10428 for space 6165 : [ 35 51 53 6b 56 42 ]. Assuming space is not encrypted!.

      Attachments

        Activity

          People

            jplindst Jan Lindström (Inactive)
            jplindst Jan Lindström (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0d
                0d
                Logged:
                Time Spent - 1h
                1h

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.