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

[Otto Kekäläinen]

Control: severity -1 normal

On Thu, Oct 21, 2021 at 9:24 PM Marc Gallet <debian-bugs at zertrin.org> wrote:
> I've been brought to this bug by apt-listbugs while doing upgrades
> on my buster install, warning me of a grave bug.

We have two users who have experienced a potentially corrupted
database (out of hundreds of thousands or even potentially millions of
users, depending how one wants to extrapolate the popcon data). A bug
report has been filed and it is kept open in case somebody could
provide a way to reproduce the bug or report something actionable.
Otherwise neither the Debian packagers nor upstream developers (and
upstream does not even know about this bug, since it is still vague
and no bug report has been filed upstream) will do anything about the
bug report.

I am now downgrading this bug report severity to "normal" so that it
will not raise false alarms for random users.

> 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.

You should have a backup anyway, that is just good practice while
maintaining database systems.

When you want to upgrade, run 'apt upgrade'.

If your database is already broken/corrupted, the upgrade will not fix
it. You can easily test your database by restarting it (and see that
it restarts), read the logs and related documentation. Official Debian
package documentation is the README files in the packaging, and they
contain more tips about best practices. I recommend you use them as
the primary source of information and don't put too much weight on a
single bug report.