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

[Yves-Alexis Perez]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

control: subscribe -1

On Sun, 10 Oct 2021 16:13:29 +0200 Ondrej Zary <zary at gsystem.sk> wrote:
> Package: mariadb-server
> Version: 1:10.3.31-0+deb10u1
> Severity: grave
> Justification: causes non-serious data loss
> 
> Dear Maintainer,
> upgrading mariadb-server from 1:10.3.29-0+deb10u1 to 1:10.3.31-0+deb10u1
failed
> because mariadb failed to start. /var/log/mysql/error.log:
> 
> 2021-10-10 15:12:49 0 [ERROR] InnoDB: corrupted TRX_NO 10002001c6986c3
> 2021-10-10 15:12:49 0 [ERROR] InnoDB: Plugin initialization aborted with
error Data structure corruption
> 2021-10-10 15:12:50 0 [ERROR] Plugin 'InnoDB' init function returned error.
> 2021-10-10 15:12:50 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE
ENGINE failed.
> 2021-10-10 15:12:50 0 [ERROR] Unknown/unsupported storage engine: InnoDB
> 2021-10-10 15:12:50 0 [ERROR] Aborting
> 
> Fortunately, it works after downgrading back to 10.3.29.
> Data does not seem to be corrupted.
> 

For what's it's worth I'm experiencing the same issue on my installation. I
took me some time to find that bug (and I started to dig how to repair innodb
stuff. Good to know downgrading should help, thanks.

Regards,
- -- 
Yves-Alexis
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmFjNSIACgkQ3rYcyPpX
RFsxlQgAo0eUU9T8XaIsYIw/jx4dmbRf9DO8/IxPvFuMw0zkn7JO2LxL61IRIcAa
SDljx7UjnJpTpJ6Nc6XXQ8sU3EIb4qUen1dRME383jcUEAN0Yh3F2cvBmNkjV7bN
rDdRf74leH76uYo9sPIgWnZwy2U2I9HVKhlD3uo2MF53ksem1yVJh3Jvll5w0ZsM
SsMCO2wTjq3RFbc38bqKASSh/+UvXAxxY/6R6bxc+YIWqsim9z8XQ9TKZXdnjPS+
aOcJblZarGOjdC2AwbeT9GVaBoaCx9V9RlQDn3WoMvVhHvjfI32j+tEG1uWnicC/
q1tnUp/9oBnvt8eYDbRY3ny3oC6ylA==
=oOyd
-----END PGP SIGNATURE-----