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

[Ondrej Zary]

On Thursday 14 October 2021, Yves-Alexis Perez wrote:
> On Thu, 2021-10-14 at 00:03 -0700, Otto Kekäläinen wrote:
> > Right. Here is for Buster:
> >
> > https://salsa.debian.org/mariadb-team/mariadb-10.3/-/commit/8ccf2240960cbb609cedfeb269df22d43ccbba21
> > https://salsa.debian.org/mariadb-team/mariadb-10.3/-/pipelines/302376
> 
> Unfortunately, with:
> 
> ii  libmariadb3:amd64              1:10.3.31-0+deb10u1+salsaci           amd64        MariaDB database client library
> ii  mariadb-client                 1:10.3.31-0+deb10u1+salsaci           all          MariaDB database client (metapackage depending on the latest version)
> ii  mariadb-client-10.3            1:10.3.31-0+deb10u1+salsaci           amd64        MariaDB database client binaries
> ii  mariadb-client-core-10.3       1:10.3.31-0+deb10u1+salsaci           amd64        MariaDB database core client binaries
> ii  mariadb-common                 1:10.3.31-0+deb10u1+salsaci           all          MariaDB common metapackage
> ii  mariadb-server                 1:10.3.31-0+deb10u1+salsaci           all          MariaDB database server (metapackage depending on the latest version)
> ii  mariadb-server-10.3            1:10.3.31-0+deb10u1+salsaci           amd64        MariaDB database server binaries
> ii  mariadb-server-core-10.3       1:10.3.31-0+deb10u1+salsaci           amd64        MariaDB database core server files
> 
> 
> I still get:
> 
> 2021-10-14  9:38:48 0 [Note] InnoDB: Using Linux native AIO
> 2021-10-14  9:38:48 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
> 2021-10-14  9:38:48 0 [Note] InnoDB: Uses event mutexes
> 2021-10-14  9:38:48 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
> 2021-10-14  9:38:48 0 [Note] InnoDB: Number of pools: 1
> 2021-10-14  9:38:48 0 [Note] InnoDB: Using SSE2 crc32 instructions
> 2021-10-14  9:38:48 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
> 2021-10-14  9:38:48 0 [Note] InnoDB: Completed initialization of buffer pool
> 2021-10-14  9:38:48 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
> 2021-10-14  9:38:48 0 [ERROR] InnoDB: corrupted TRX_NO 10002001a6990af
> 2021-10-14  9:38:48 0 [Note] InnoDB: Retry with innodb_force_recovery=5
> 2021-10-14  9:38:48 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
> 2021-10-14  9:38:49 0 [Note] InnoDB: Starting shutdown...
> 2021-10-14  9:38:49 0 [ERROR] Plugin 'InnoDB' init function returned error.
> 2021-10-14  9:38:49 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
> 2021-10-14  9:38:49 0 [Note] Plugin 'FEEDBACK' is disabled.
> 2021-10-14  9:38:49 0 [ERROR] Unknown/unsupported storage engine: InnoDB
> 2021-10-14  9:38:49 0 [ERROR] Aborting
> 
> So maybe I do have a corrupted database or something but I'm unsure what to do
> next (I don't think I have an older backups of the database). Also it still
> works just fine with 10.3.25.

I still get the error too. That patch was meant to fix a problem specific to BSD.

-- 
Ondrej Zary