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

[Otto Kekäläinen]

On Tue, Mar 29, 2022 at 9:33 PM Johnny A. Solbu <johnny at solbu.net> wrote:
>
> 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?

Please keep in mind that this is an open source project. You are
welcome to debug the issue yourself and to contribute towards a fix
for it. If you need somebody else to fix it for you, you might
consider using a consultant or a support provider to investigate your
particular installation and make fixes for your particular instance.

https://www.debian.org/consultants/
https://mariadb.org/about/#service-providers