Your message dated Sun, 20 Nov 2022 16:58:50 -0800
with message-id
<CAOU6tAAMKcFXPVG-VcnTZ0CwLMgKVQ4J0Nt1VjhKN53Ww=d...@mail.gmail.com>
and subject line Re: [debian-mysql] Bug#996028: Bug#996028: Bug#996028: InnoDB:
corrupted TRX_NO after upgrading to 10.3.31
has caused the Debian Bug report #996028,
regarding InnoDB: corrupted TRX_NO after upgrading to 10.3.31
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
996028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996028
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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.
-- System Information:
Debian Release: 10.11
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: i386 (x86_64)
Foreign Architectures: amd64
Kernel: Linux 4.19.0-17-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=sk_SK.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)
Versions of packages mariadb-server depends on:
ii mariadb-server-10.3 1:10.3.31-0+deb10u1
mariadb-server recommends no packages.
mariadb-server suggests no packages.
-- debconf-show failed
--- End Message ---
--- Begin Message ---
Version: 1:10.3.34-0+deb10u1
The upstream issue https://jira.mariadb.org/browse/MDEV-26537 was
fixed in MariaDB 10.3.32 / 10.5.13 / 10.6.5 which are all in various
Debian releases for some time already.
As nobody was able to provide steps on how to reproduce the issue you
experienced, it is impossible for me to test this. You could get hire
a Debian consultant or some other person to investigate the specific
issue you had on your machine if it is a production system.
Since there hasn't been any new comments for a while, I assume at
least some people who reported this did hit
https://jira.mariadb.org/browse/MDEV-26537, and that is fixed, so I am
closing this bug report.
If you want to help out with developing future versions of MariaDB
updates for Debian, see
https://salsa.debian.org/mariadb-team/mariadb-server/-/wikis/Contributing-to-MariaDB-packaging-in-Debian
--- End Message ---
