Status: Closed (View Workflow)
Affects Version/s: 10.2.8
Environment:RH Linux 3.10.0-957.21.3.el7.x86_64, VMWare
4CPU 16GB RAM
In a Mariadb replication setup (1 master, 1 slave)
We got an
InnoDB: Page 38:4016 may be corrupted. Post encryption checksum 3690179534 stored [3690179534:3690179534] key_version
for no obvious reason, no HW failure or anything noticeable at OS level.
Then a bit later : Got error 192 when reading table
We had to switch role to let the application operate again. That went OK, although we lost the rows that could not be replicated for the corrupted table.
After a while, the old master that was promoted to slaved crashed an could not be restarted, besides using recovery level 6.
We ended resyncing with full backup but the issue is scary.
Asking for analysis and feedback.