[MDEV-18279] MLOG_FILE_WRITE_CRYPT_DATA fails to set the crypt_data->type for tablespace. - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.1(EOL), 10.2(EOL), 10.3(EOL), 10.4(EOL)
Fix Version/s: 10.4.2, 10.1.38, 10.2.22, 10.3.13
Component/s: Storage Engine - InnoDB
Labels:
None

Description

The following patch can able to repeat the issue:

diff --git a/mysql-test/suite/encryption/t/innodb-encryption-alter.test b/mysql-test/suite/encryption/t/innodb-encryption-alter.test

index e8391d9..8af0bfa 100644

--- a/mysql-test/suite/encryption/t/innodb-encryption-alter.test

+++ b/mysql-test/suite/encryption/t/innodb-encryption-alter.test

@@ -105,6 +105,18 @@ DROP TABLE t2;

 CREATE TABLE t3 (a int not null primary key) engine=innodb ENCRYPTION_KEY_ID=4;

 SHOW WARNINGS;

+--let datadir= `select @@datadir`

+--let $_server_id= `SELECT @@server_id`

+--let $_expect_file_name= $MYSQLTEST_VARDIR/tmp/mysqld.$_server_id.expect

+create table t1(f1 int not null, f2 int not null)engine=innodb encrypted=yes;

+insert into t1 values(1, 2), (2, 3), (4, 5), (5, 6), (7, 8);

+insert into t1 select * from t1;

+--source include/kill_mysqld.inc

+--source include/start_mysqld.inc

+select * from t1;

+drop table t1;

It gives the warning messages like:

10.2 f3e9d9a6e6b2614bf5d57ccf9434c980e4a90424
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=329] is corrupted.
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=337] is corrupted.
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=446] is corrupted.
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=366] is corrupted.
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=450] is corrupted.
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=451] is corrupted.
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=375] is corrupted.
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=384] is corrupted.
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=393] is corrupted.

Attachments

Issue Links

relates to

MDEV-18183 Server startup fails while dropping garbage encrypted tablespace

Closed

Activity

Ascending order - Click to sort in descending order

Thirunarayanan Balathandayuthapani created issue - 2019-01-17 06:26

Thirunarayanan Balathandayuthapani made changes - 2019-01-17 07:34

Field	Original Value	New Value
Description	Problem is that redo log fails to apply type for the crypt_data present in the space. The following patch can able to repeat the issue: diff --git a/mysql-test/suite/encryption/t/innodb-encryption-alter.test b/mysql-test/suite/encryption/t/innodb-encryption-alter.test index e8391d9..8af0bfa 100644 --- a/mysql-test/suite/encryption/t/innodb-encryption-alter.test +++ b/mysql-test/suite/encryption/t/innodb-encryption-alter.test @@ -105,6 +105,18 @@ DROP TABLE t2; CREATE TABLE t3 (a int not null primary key) engine=innodb ENCRYPTION_KEY_ID=4; SHOW WARNINGS; +--let datadir= `select @@datadir` +--let $_server_id= `SELECT @@server_id` +--let $_expect_file_name= $MYSQLTEST_VARDIR/tmp/mysqld.$_server_id.expect + +create table t1(f1 int not null, f2 int not null)engine=innodb encrypted=yes; +insert into t1 values(1, 2), (2, 3), (4, 5), (5, 6), (7, 8); +insert into t1 select * from t1; +--source include/kill_mysqld.inc +--source include/start_mysqld.inc +select * from t1; +drop table t1; + It gives the warning messages like: 2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=329] is corrupted. 2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=337] is corrupted. 2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=446] is corrupted. 2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=366] is corrupted. 2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=450] is corrupted. 2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=451] is corrupted. 2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=375] is corrupted. 2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=384] is corrupted. 2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=393] is corrupted.	Problem is that MLOG_FILE_WRITE_CRYPT_DATA redo log fails to apply type for the crypt_data present in the space. While processing the double-write buffe pages, page fails to decrypt because fil_space_t doesn't have type. The following patch can able to repeat the issue: {code} diff --git a/mysql-test/suite/encryption/t/innodb-encryption-alter.test b/mysql-test/suite/encryption/t/innodb-encryption-alter.test index e8391d9..8af0bfa 100644 --- a/mysql-test/suite/encryption/t/innodb-encryption-alter.test +++ b/mysql-test/suite/encryption/t/innodb-encryption-alter.test @@ -105,6 +105,18 @@ DROP TABLE t2; CREATE TABLE t3 (a int not null primary key) engine=innodb ENCRYPTION_KEY_ID=4; SHOW WARNINGS; +--let datadir= `select @@datadir` +--let $_server_id= `SELECT @@server_id` +--let $_expect_file_name= $MYSQLTEST_VARDIR/tmp/mysqld.$_server_id.expect + +create table t1(f1 int not null, f2 int not null)engine=innodb encrypted=yes; +insert into t1 values(1, 2), (2, 3), (4, 5), (5, 6), (7, 8); +insert into t1 select * from t1; +--source include/kill_mysqld.inc +--source include/start_mysqld.inc +select * from t1; +drop table t1; + {code} Above patch is repeatable in this revision: {noformat:title=10.2 f3e9d9a6e6b2614bf5d57ccf9434c980e4a90424} {noformat} It gives the warning messages like: {code} 2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=329] is corrupted. 2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=337] is corrupted. 2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=446] is corrupted. 2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=366] is corrupted. 2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=450] is corrupted. 2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=451] is corrupted. 2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=375] is corrupted. 2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=384] is corrupted. 2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=393] is corrupted. {code}

Thirunarayanan Balathandayuthapani made changes - 2019-01-17 07:42

Fix Version/s		10.1.38 [ 23209 ]
Fix Version/s		10.3.13 [ 23215 ]
Fix Version/s		10.2.22 [ 23250 ]
Fix Version/s		10.4.1 [ 23228 ]
Resolution		Fixed [ 1 ]
Status	Open [ 1 ]	Closed [ 6 ]

Marko Mäkelä made changes - 2019-01-17 09:29

Description

Problem is that MLOG_FILE_WRITE_CRYPT_DATA redo log fails to apply type for the crypt_data present in the space. While processing the double-write buffe
pages, page fails to decrypt because fil_space_t doesn't have type.

The following patch can able to repeat the issue:
{code}
diff --git a/mysql-test/suite/encryption/t/innodb-encryption-alter.test b/mysql-test/suite/encryption/t/innodb-encryption-alter.test
index e8391d9..8af0bfa 100644
--- a/mysql-test/suite/encryption/t/innodb-encryption-alter.test
+++ b/mysql-test/suite/encryption/t/innodb-encryption-alter.test
@@ -105,6 +105,18 @@ DROP TABLE t2;
CREATE TABLE t3 (a int not null primary key) engine=innodb ENCRYPTION_KEY_ID=4;
SHOW WARNINGS;

+--let datadir= `select @@datadir`
+--let $_server_id= `SELECT @@server_id`
+--let $_expect_file_name= $MYSQLTEST_VARDIR/tmp/mysqld.$_server_id.expect
+
+create table t1(f1 int not null, f2 int not null)engine=innodb encrypted=yes;
+insert into t1 values(1, 2), (2, 3), (4, 5), (5, 6), (7, 8);
+insert into t1 select * from t1;
+--source include/kill_mysqld.inc
+--source include/start_mysqld.inc
+select * from t1;
+drop table t1;
+
{code}

Above patch is repeatable in this revision: {noformat:title=10.2 f3e9d9a6e6b2614bf5d57ccf9434c980e4a90424} {noformat}
It gives the warning messages like:

{code}
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=329] is corrupted.
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=337] is corrupted.
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=446] is corrupted.
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=366] is corrupted.
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=450] is corrupted.
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=451] is corrupted.
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=375] is corrupted.
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=384] is corrupted.
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=393] is corrupted.
{code}

Problem is that MLOG_FILE_WRITE_CRYPT_DATA redo log fails to apply type for the crypt_data present in the space. While processing the double-write buffe
pages, page fails to decrypt because fil_space_t doesn't have type.

The following patch can able to repeat the issue:
{code}
diff --git a/mysql-test/suite/encryption/t/innodb-encryption-alter.test b/mysql-test/suite/encryption/t/innodb-encryption-alter.test
index e8391d9..8af0bfa 100644
--- a/mysql-test/suite/encryption/t/innodb-encryption-alter.test
+++ b/mysql-test/suite/encryption/t/innodb-encryption-alter.test
@@ -105,6 +105,18 @@ DROP TABLE t2;
CREATE TABLE t3 (a int not null primary key) engine=innodb ENCRYPTION_KEY_ID=4;
SHOW WARNINGS;

+--let datadir= `select @@datadir`
+--let $_server_id= `SELECT @@server_id`
+--let $_expect_file_name= $MYSQLTEST_VARDIR/tmp/mysqld.$_server_id.expect
+
+create table t1(f1 int not null, f2 int not null)engine=innodb encrypted=yes;
+insert into t1 values(1, 2), (2, 3), (4, 5), (5, 6), (7, 8);
+insert into t1 select * from t1;
+--source include/kill_mysqld.inc
+--source include/start_mysqld.inc
+select * from t1;
+drop table t1;
+
{code}

It gives the warning messages like:
{noformat:title=10.2 f3e9d9a6e6b2614bf5d57ccf9434c980e4a90424}
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=329] is corrupted.
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=337] is corrupted.
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=446] is corrupted.
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=366] is corrupted.
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=450] is corrupted.
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=451] is corrupted.
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=375] is corrupted.
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=384] is corrupted.
2019-01-17 11:54:52 139736940791616 [Warning] InnoDB: A doublewrite copy of page [page id: space=0, page number=393] is corrupted.
{noformat}

Marko Mäkelä made changes - 2019-01-17 09:32

Link

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

Marko Mäkelä made changes - 2019-01-17 12:41

Fix Version/s		10.4.2 [ 23229 ]
Fix Version/s	10.4.1 [ 23228 ]

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

Workflow

MariaDB v3 [ 91782 ]

MariaDB v4 [ 155542 ]

People

Assignee:: Thirunarayanan Balathandayuthapani

Reporter:: Thirunarayanan Balathandayuthapani

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 2019-01-17 06:26

Updated:: 2019-01-22 12:31

Resolved:: 2019-01-17 07:42

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