[MDEV-7803] Encryption metadata (crypt_data) is written to InnoDB file space page 0 even when encryption is not enabled Created: 2015-03-19  Updated: 2015-03-19  Resolved: 2015-03-19

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB, Storage Engine - XtraDB
Affects Version/s: 10.1.3
Fix Version/s: 10.1.4

Type: Bug Priority: Critical
Reporter: Jan Lindström (Inactive) Assignee: Jan Lindström (Inactive)
Resolution: Fixed Votes: 0
Labels: None


 Description   
  • When innodb_encrypt_tablespace == FALSE and fil_space_page_encrypted(space) == FALSE make sure that no encryption data is written to file space page 0 and redo-logs.
  • If we have existing database that is not encrypted make sure that encryption can be enabled and all existing file spaces are encrypted (Google encryption).

 Comments   
Comment by Jan Lindström (Inactive) [ 2015-03-19 ]

commit b3438f24a17a28b2d396208a1bb072199cef5f39
Author: Jan Lindström <jan.lindstrom@mariadb.com>
Date: Thu Mar 19 14:09:49 2015 +0200

MDEV-7803: Encryption metadata (crypt_data) is written to InnoDB file space page 0 e
ven when encryption is not enabled

Generated at Thu Feb 08 07:22:23 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.