Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.6.12, 10.6.14
-
None
-
unbuntu 20.04
Description
We have master-salve replication with table encryption and with aws-key-management plugin
On the master :
innodb_encrypt_tables = Off
|
innodb_encrypt_log = Off
|
innodb_encryption_threads = 0
|
on the slave:
innodb_encrypt_tables = On
|
innodb_encrypt_log = Off
|
innodb_encryption_threads = 4
|
First we got this messages :
[Note] InnoDB: Cannot close file ./database/table.ibd because of pending fsync
After this the server crashed with this error message
[ERROR] InnoDB: Operating system error number 9 in a file operation.
|
[ERROR] InnoDB: Error number 9 means 'Bad file descriptor'
|
[Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
|
[ERROR] InnoDB: File (unknown): 'close' returned OS error 209. Cannot continue operation
|
230420 20:18:35 [ERROR] mysqld got signal 6 ;
|
This could be because you hit a bug. It is also possible that this binary
|
or one of the libraries it was linked against is corrupt, improperly built,
|
or misconfigured. This error can also be caused by malfunctioning hardware.
|
Atfer start up
[ERROR] InnoDB: Cannot decrypt [page id: space=2890523, page number=384]
and another time:
[Warning] InnoDB: 16384 bytes should have been read at 1174798336 from ./database/table.ibd, but got only 0. Retrying.
After this the table was corrupted, can't acess, alter, can't repair table.
Our solution is on the slave (after reload databse from master) :
innodb_encryption_threads = 0
Attachments
Issue Links
- relates to
-
-
- Closed
-