[debian-mysql] Bug#996028: Bug#996028: InnoDB: corrupted TRX_NO after upgrading to 10.3.31

[Johnny A. Solbu]

On Sunday 20 February 2022 02:23, Otto Kekäläinen wrote:
> Is the issue https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996028
> still affecting people?

We just hit it again on our server aftre4r upgrading just now, and I am not sure why.
We had to resort to enableing «innodb_force_recovery = 5» just to get the mariadb server started.


I am not sure how we are supposed to fix it.
There is no clear guidance as to how we are supposed to fix this, not that i can see anyway.

Is there a _Clear_ and _simple_ explanation/guide as to how we are supposed to fix this on our end?


-- 
Johnny A. Solbu
web site,   https://www.solbu.net
PGP key ID: 0x4F5AD64DFA687324
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-mysql-maint/attachments/20220330/8f9d57b9/attachment.sig>