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

[Marc Gallet]

Package: mariadb-server
Followup-For: Bug #996028

Hi,

I've been brought to this bug by apt-listbugs while doing upgrades
on my buster install, warning me of a grave bug.

I have not attempted the upgrade yet, since, after reading this bug, I
see a risk of data corruption and I would like to avoid going into
recovery procedures (from backups) as a result of what should be a
stable upgrade.

It seems there was an attempt at fixing the problem for buster, but this
hasn't been pushed as a new version yet, right?

Am I correct to assume this issue is still relevant for buster and that
for now, I should simply defer the upgrade (marking the packages to be
held back) and simply wait for this bug to be resolved?

Thanks

-- System Information:
Debian Release: 10.11
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-18-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mariadb-server depends on:
hi  mariadb-server-10.3  1:10.3.29-0+deb10u1

mariadb-server recommends no packages.

mariadb-server suggests no packages.

-- no debconf information