[MDEV-17231] Encryption threads keep re-encrypting/encrypting corrupted pages Created: 2018-09-18 Updated: 2021-12-27 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Encryption, Storage Engine - InnoDB |
| Affects Version/s: | 10.2 |
| Fix Version/s: | 10.2 |
| Type: | Bug | Priority: | Major |
| Reporter: | Robert Golebiowski | Assignee: | Thirunarayanan Balathandayuthapani |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Although page of a table is corrupted it will still be encrypted/re-encrypted by encryption threads. MariaDB will report table as successfully encrypted/re-encrypted although there can be corrupted pages which could not be read. Spaces which contain corrupted pages should be skipped. |
| Comments |
| Comment by Elena Stepanova [ 2018-09-18 ] |
|
It sounds rather arbitrary, I don't really see why tablespaces with corrupt pages must be skipped, why it's better than not skipping them (if there is anything "better" for the garbage-in situation). I'll leave it to jplindst to decide whether he wants to change anything or close it. |
| Comment by Robert Golebiowski [ 2018-09-18 ] |
|
Encrypted pages that were not decrypted properly will also get re-encrypted when key rotates. This means that garbage will get encrypted and reported "encrypted successfully" . It should not be allowed, as this means no way of getting to the original data and lose of data. |