[MDEV-19335] Removal of encrypted from buf_page_t - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.3.14
Fix Version/s: 10.2.28, 10.3.19, 10.4.9
Component/s: Encryption, Storage Engine - InnoDB
Labels:
None

Description

A data import (using SQLines as import tool) into encrypted tables failed with:

SHOW WARNINGS: LOAD DATA LOCAL INFILE 'filename' IGNORE INTO

TABLE db_name.table:name

Level: Warning; Code: 192; Message: Table

db_name.table_name is encrypted but encryption service or used

key_id is not available. Can't continue reading table.

Level: Warning; Code: 192; Message: Table

db_name.table_name is encrypted but encryption service or used

key_id is not available. Can't continue reading table.

Level: Error; Code: 1296; Message: Got error 192 'Table encrypted but

decryption failed. This could be because correct encryption management

plugin is not loaded, used encryption key is not available or encryption

method does not match.' from InnoDB

Simple file_key_management is used to manage encryption keys,
all tables use the same key id, and there has only been a single
key version.

Still just this one table reports encryption key errors, while other
encrypted tables using the same key id and version still work fine.

E.g. when checing tablespace encryption information for the table "table_name" triggering the error, and another table "other_table" that works fine, there are no visible differences apart from the space number and table name:

SELECT * FROM

INFORMATION_SCHEMA.INNODB_TABLESPACES_ENCRYPTION

WHERE NAME in

('db_name/table_name', 'db_name/other_table')\G

*************************** 1. row ***************************

SPACE: 3406

NAME: db_name/other_table

ENCRYPTION_SCHEME: 1

KEYSERVER_REQUESTS: 1

MIN_KEY_VERSION: 1

CURRENT_KEY_VERSION: 1

KEY_ROTATION_PAGE_NUMBER: NULL

KEY_ROTATION_MAX_PAGE_NUMBER: NULL

CURRENT_KEY_ID: 1

ROTATING_OR_FLUSHING: 0

*************************** 2. row ***************************

SPACE: 3449

NAME: db_name/table_name

ENCRYPTION_SCHEME: 1

KEYSERVER_REQUESTS: 1

MIN_KEY_VERSION: 1

CURRENT_KEY_VERSION: 1

KEY_ROTATION_PAGE_NUMBER: NULL

KEY_ROTATION_MAX_PAGE_NUMBER: NULL

CURRENT_KEY_ID: 1

ROTATING_OR_FLUSHING: 0

Error log repeatedly contains:

[ERROR] InnoDB: Failed to read file

'./db_name/table_name.ibd' at offset 1162674: Table is

encrypted but decrypt failed.

[ERROR] InnoDB: The page [page id: space=3449, page

number=1162674] in file './db_name/table_name.ibd' cannot be

decrypted.

[Note] InnoDB: However key management plugin or used key_version

1 is not found or used encryption algorithm or method does not match.

[Note] InnoDB: Marking tablespace as missing. You may drop this

table or install correct key management plugin and key file.

Attachments

Issue Links

relates to

MDEV-12699 Improve crash recovery of corrupted data pages

Closed

Activity

Ascending order - Click to sort in descending order

Hartmut Holzgraefe created issue - 2019-04-25 13:05

Hartmut Holzgraefe made changes - 2019-04-25 14:30

Field	Original Value	New Value
Description	A data import (using SQLines as import tool) into encrypted tables failed with: {noformat} SHOW WARNINGS: LOAD DATA LOCAL INFILE 'filename' IGNORE INTO TABLE db_name.table:name Level: Warning; Code: 192; Message: Table db_name.table_name is encrypted but encryption service or used key_id is not available. Can't continue reading table. Level: Warning; Code: 192; Message: Table db_name.table_name is encrypted but encryption service or used key_id is not available. Can't continue reading table. Level: Error; Code: 1296; Message: Got error 192 'Table encrypted but decryption failed. This could be because correct encryption management plugin is not loaded, used encryption key is not available or encryption method does not match.' from InnoDB {noformat} Simple file_key_management is used to manage encryption keys, all tables use the same key id, and there has only been a single key version. Still just this one table reports encryption key errors, while other encrypted tables using the same key id and version still work fine. E.g.: {noformat} SELECT * FROM INFORMATION_SCHEMA.INNODB_TABLESPACES_ENCRYPTION WHERE NAME in ('db_name/table_name', 'db_name/other_table')\G ************************* 1. row *********************** SPACE: 3406 NAME: db_name/other_table ENCRYPTION_SCHEME: 1 KEYSERVER_REQUESTS: 1 MIN_KEY_VERSION: 1 CURRENT_KEY_VERSION: 1 KEY_ROTATION_PAGE_NUMBER: NULL KEY_ROTATION_MAX_PAGE_NUMBER: NULL CURRENT_KEY_ID: 1 ROTATING_OR_FLUSHING: 0 *********************** 2. row ************************* SPACE: 3449 NAME: db_name/table_name ENCRYPTION_SCHEME: 1 KEYSERVER_REQUESTS: 1 MIN_KEY_VERSION: 1 CURRENT_KEY_VERSION: 1 KEY_ROTATION_PAGE_NUMBER: NULL KEY_ROTATION_MAX_PAGE_NUMBER: NULL CURRENT_KEY_ID: 1 ROTATING_OR_FLUSHING: 0 {noformat}	A data import (using SQLines as import tool) into encrypted tables failed with: {noformat} SHOW WARNINGS: LOAD DATA LOCAL INFILE 'filename' IGNORE INTO TABLE db_name.table:name Level: Warning; Code: 192; Message: Table db_name.table_name is encrypted but encryption service or used key_id is not available. Can't continue reading table. Level: Warning; Code: 192; Message: Table db_name.table_name is encrypted but encryption service or used key_id is not available. Can't continue reading table. Level: Error; Code: 1296; Message: Got error 192 'Table encrypted but decryption failed. This could be because correct encryption management plugin is not loaded, used encryption key is not available or encryption method does not match.' from InnoDB {noformat} Simple file_key_management is used to manage encryption keys, all tables use the same key id, and there has only been a single key version. Still just this one table reports encryption key errors, while other encrypted tables using the same key id and version still work fine. E.g.: {noformat} SELECT * FROM INFORMATION_SCHEMA.INNODB_TABLESPACES_ENCRYPTION WHERE NAME in ('db_name/table_name', 'db_name/other_table')\G ************************* 1. row *********************** SPACE: 3406 NAME: db_name/other_table ENCRYPTION_SCHEME: 1 KEYSERVER_REQUESTS: 1 MIN_KEY_VERSION: 1 CURRENT_KEY_VERSION: 1 KEY_ROTATION_PAGE_NUMBER: NULL KEY_ROTATION_MAX_PAGE_NUMBER: NULL CURRENT_KEY_ID: 1 ROTATING_OR_FLUSHING: 0 *********************** 2. row ************************* SPACE: 3449 NAME: db_name/table_name ENCRYPTION_SCHEME: 1 KEYSERVER_REQUESTS: 1 MIN_KEY_VERSION: 1 CURRENT_KEY_VERSION: 1 KEY_ROTATION_PAGE_NUMBER: NULL KEY_ROTATION_MAX_PAGE_NUMBER: NULL CURRENT_KEY_ID: 1 ROTATING_OR_FLUSHING: 0 {noformat} Error log repeatedly contains: {noformat} [ERROR] InnoDB: Failed to read file './db_name/table_name.ibd' at offset 1162674: Table is encrypted but decrypt failed. [ERROR] InnoDB: The page [page id: space=3449, page number=1162674] in file './db_name/table_name.ibd' cannot be decrypted. [Note] InnoDB: However key management plugin or used key_version 1 is not found or used encryption algorithm or method does not match. [Note] InnoDB: Marking tablespace as missing. You may drop this table or install correct key management plugin and key file. {noformat}

Hartmut Holzgraefe made changes - 2019-04-25 14:32

Description

A data import (using SQLines as import tool) into encrypted tables failed with:

{noformat}
SHOW WARNINGS: LOAD DATA LOCAL INFILE 'filename' IGNORE INTO
TABLE db_name.table:name
Level: Warning; Code: 192; Message: Table
db_name.table_name is encrypted but encryption service or used
key_id is not available. Can't continue reading table.
Level: Warning; Code: 192; Message: Table
db_name.table_name is encrypted but encryption service or used
key_id is not available. Can't continue reading table.
Level: Error; Code: 1296; Message: Got error 192 'Table encrypted but
decryption failed. This could be because correct encryption management
plugin is not loaded, used encryption key is not available or encryption
method does not match.' from InnoDB
{noformat}

Simple file_key_management is used to manage encryption keys,
all tables use the same key id, and there has only been a single
key version.

Still just this one table reports encryption key errors, while other
encrypted tables using the same key id and version still work fine.

E.g.:

{noformat}
SELECT * FROM
INFORMATION_SCHEMA.INNODB_TABLESPACES_ENCRYPTION
WHERE NAME in
('db_name/table_name', 'db_name/other_table')\G
*************************** 1. row ***************************
SPACE: 3406
NAME: db_name/other_table
ENCRYPTION_SCHEME: 1
KEYSERVER_REQUESTS: 1
MIN_KEY_VERSION: 1
CURRENT_KEY_VERSION: 1
KEY_ROTATION_PAGE_NUMBER: NULL
KEY_ROTATION_MAX_PAGE_NUMBER: NULL
CURRENT_KEY_ID: 1
ROTATING_OR_FLUSHING: 0
*************************** 2. row ***************************
SPACE: 3449
NAME: db_name/table_name
ENCRYPTION_SCHEME: 1
KEYSERVER_REQUESTS: 1
MIN_KEY_VERSION: 1
CURRENT_KEY_VERSION: 1
KEY_ROTATION_PAGE_NUMBER: NULL
KEY_ROTATION_MAX_PAGE_NUMBER: NULL
CURRENT_KEY_ID: 1
ROTATING_OR_FLUSHING: 0
{noformat}

Error log repeatedly contains:

{noformat}
[ERROR] InnoDB: Failed to read file
'./db_name/table_name.ibd' at offset 1162674: Table is
encrypted but decrypt failed.
[ERROR] InnoDB: The page [page id: space=3449, page
number=1162674] in file './db_name/table_name.ibd' cannot be
decrypted.
[Note] InnoDB: However key management plugin or used key_version
1 is not found or used encryption algorithm or method does not match.
[Note] InnoDB: Marking tablespace as missing. You may drop this
table or install correct key management plugin and key file.
{noformat}

A data import (using SQLines as import tool) into encrypted tables failed with:

{noformat}
SHOW WARNINGS: LOAD DATA LOCAL INFILE 'filename' IGNORE INTO
TABLE db_name.table:name
Level: Warning; Code: 192; Message: Table
db_name.table_name is encrypted but encryption service or used
key_id is not available. Can't continue reading table.
Level: Warning; Code: 192; Message: Table
db_name.table_name is encrypted but encryption service or used
key_id is not available. Can't continue reading table.
Level: Error; Code: 1296; Message: Got error 192 'Table encrypted but
decryption failed. This could be because correct encryption management
plugin is not loaded, used encryption key is not available or encryption
method does not match.' from InnoDB
{noformat}

Simple file_key_management is used to manage encryption keys,
all tables use the same key id, and there has only been a single
key version.

Still just this one table reports encryption key errors, while other
encrypted tables using the same key id and version still work fine.

E.g. when checing tablespace encryption information for the table "table_name" triggering the error, and another table "other_table" that works fine, there are no visible differences apart from the space number and table name:

{noformat}
SELECT * FROM
INFORMATION_SCHEMA.INNODB_TABLESPACES_ENCRYPTION
WHERE NAME in
('db_name/table_name', 'db_name/other_table')\G
*************************** 1. row ***************************
SPACE: 3406
NAME: db_name/other_table
ENCRYPTION_SCHEME: 1
KEYSERVER_REQUESTS: 1
MIN_KEY_VERSION: 1
CURRENT_KEY_VERSION: 1
KEY_ROTATION_PAGE_NUMBER: NULL
KEY_ROTATION_MAX_PAGE_NUMBER: NULL
CURRENT_KEY_ID: 1
ROTATING_OR_FLUSHING: 0
*************************** 2. row ***************************
SPACE: 3449
NAME: db_name/table_name
ENCRYPTION_SCHEME: 1
KEYSERVER_REQUESTS: 1
MIN_KEY_VERSION: 1
CURRENT_KEY_VERSION: 1
KEY_ROTATION_PAGE_NUMBER: NULL
KEY_ROTATION_MAX_PAGE_NUMBER: NULL
CURRENT_KEY_ID: 1
ROTATING_OR_FLUSHING: 0
{noformat}

Error log repeatedly contains:

{noformat}
[ERROR] InnoDB: Failed to read file
'./db_name/table_name.ibd' at offset 1162674: Table is
encrypted but decrypt failed.
[ERROR] InnoDB: The page [page id: space=3449, page
number=1162674] in file './db_name/table_name.ibd' cannot be
decrypted.
[Note] InnoDB: However key management plugin or used key_version
1 is not found or used encryption algorithm or method does not match.
[Note] InnoDB: Marking tablespace as missing. You may drop this
table or install correct key management plugin and key file.
{noformat}

Elena Stepanova made changes - 2019-04-28 20:18

Fix Version/s		10.3 [ 22126 ]
Assignee		Marko Mäkelä [ marko ]

Thirunarayanan Balathandayuthapani made changes - 2019-04-29 09:45

Assignee

Marko Mäkelä [ marko ]

Thirunarayanan Balathandayuthapani [ thiru ]

Thirunarayanan Balathandayuthapani made changes - 2019-05-07 08:45

Status

Open [ 1 ]

In Progress [ 3 ]

Marko Mäkelä made changes - 2019-10-03 11:14

Link

This issue relates to ~~MDEV-12699~~ [ ~~MDEV-12699~~ ]

Thirunarayanan Balathandayuthapani made changes - 2019-10-03 12:41

Summary

decryption failure on a single table

Removal of encrypted from buf_page_t

Thirunarayanan Balathandayuthapani made changes - 2019-10-03 12:43

Assignee	Thirunarayanan Balathandayuthapani [ thiru ]	Marko Mäkelä [ marko ]
Status	In Progress [ 3 ]	In Review [ 10002 ]

Marko Mäkelä made changes - 2019-10-08 15:47

Fix Version/s		10.2 [ 14601 ]
Fix Version/s		10.4 [ 22408 ]

Marko Mäkelä made changes - 2019-10-09 10:27

issue.field.resolutiondate

2019-10-09 10:27:07.0

2019-10-09 10:27:07.754

Marko Mäkelä made changes - 2019-10-09 10:27

Fix Version/s		10.2.28 [ 23910 ]
Fix Version/s		10.3.19 [ 23908 ]
Fix Version/s		10.4.9 [ 23906 ]
Fix Version/s	10.2 [ 14601 ]
Fix Version/s	10.3 [ 22126 ]
Fix Version/s	10.4 [ 22408 ]
Assignee	Marko Mäkelä [ marko ]	Thirunarayanan Balathandayuthapani [ thiru ]
Resolution		Fixed [ 1 ]
Status	In Review [ 10002 ]	Closed [ 6 ]

Marko Mäkelä made changes - 2019-10-10 12:52

Comment

[ Pushed to a staging three of 10.2 for additional testing. ]

Sergei Golubchik made changes - 2021-12-06 21:49

Workflow

MariaDB v3 [ 96358 ]

MariaDB v4 [ 156117 ]

Jira Automation (IT) made changes - 2024-07-04 04:03

Zendesk Related Tickets

148077

People

Assignee:: Thirunarayanan Balathandayuthapani

Reporter:: Hartmut Holzgraefe

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Dates

Created:: 2019-04-25 13:05

Updated:: 2024-07-07 22:49

Resolved:: 2019-10-09 10:27

Git Integration

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

MariaDB Server

Details

Description

Attachments

Issue Links

Activity

People

Dates

Git Integration