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

[Yves-Alexis Perez]

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

On Tue, 2021-10-12 at 21:58 +0200, Ondrej Zary wrote:
> > One thing you could also try is to start the server with 10.3.29 and
> > ensure that you have a clean shutdown (SET GLOBAL
> > innodb_fast_shutdown=0; SHUTDOWN) and only after that start with the
> > new 10.3.31 binary.
> 
> With fast shutdown disabled, mysqld (10.3.29) seems to be stuck in an infinite
> loop. 100% CPU usage, no I/O for an hour until I killed it.
> Even dropping all the databases did not help - killed it after it has been
> running for 5 minutes.

I tried that as well and for now the shutdown process seems a bit stuck:

2021-10-13  8:50:01 0 [Note] /usr/sbin/mysqld (initiated by: unknown): Normal
shutdown
2021-10-13  8:50:01 0 [Note] Event Scheduler: Purging the queue. 0 events
2021-10-13  8:50:01 0 [Note] InnoDB: FTS optimize thread exiting.
2021-10-13  8:50:01 4 [Note] InnoDB: to purge 5 transactions
2021-10-13  8:50:01 0 [Note] InnoDB: Starting shutdown...
2021-10-13  8:50:01 0 [Note] InnoDB: Dumping buffer pool(s) to
/var/lib/mysql/ib_buffer_pool
2021-10-13  8:50:01 0 [Note] InnoDB: Buffer pool(s) dump completed at 211013 
8:50:01
2021-10-13  8:51:02 0 [Note] InnoDB: Waiting for master thread to exit
2021-10-13  8:51:03 0 [Note] InnoDB: Waiting for change buffer merge to
complete number of bytes of change buffer just merged: 1251
2021-10-13  8:52:02 0 [Note] InnoDB: Waiting for master thread to exit
[...]
2021-10-13  9:02:05 0 [Note] InnoDB: Waiting for master thread to exit
2021-10-13  9:02:14 0 [Note] InnoDB: Waiting for change buffer merge to
complete number of bytes of change buffer just merged: 746
2021-10-13  9:03:05 0 [Note] InnoDB: Waiting for master thread to exit
2021-10-13  9:03:15 0 [Note] InnoDB: Waiting for change buffer merge to
complete number of bytes of change buffer just merged: 1040

I don't think anything still uses MySQL/MariaDB (I've stopped apache2 just in
case). I'll let it run a bit but I'm not really confident with that shutdown
process.

I've tried to rebuild mariadb-10.3 with the patch upstream committed, but it
doesn't apply to 10.3.31 directly so I stalled a bit.

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

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmFmhToACgkQ3rYcyPpX
RFuQFwf/Y7hPWdNmI//ZVnT3k2H1Jn47kOKttff4cg+RDc4LzbQX/NoQkrDaOwJJ
Yef7ne3a4FhTnkL4+L1yq8/53L22zaVvAxrXEmSgcqSvVPap0v4x6S5MXXvPhSsN
961LWuTQwdY3qSiXTRqUtKh3fgQBxBdqoWK9zT2AE0zGh04/XhaoauZ1MmH4s+T/
uX5IGtu4a8DhPQ2bno/mu421bsIndn8rkTBzaXPEh9QAd0wexMJyul6kLe4rJ2ym
zvRvYeIO4Bx8YzGV1+CuN2rtAEOGrplf3qRmBFkb1Jo7nNX8SdjaK4NqgZHAaDx9
WdEsaa6cGtoKLvNbadUJaoQ+r922cA==
=4Lb3
-----END PGP SIGNATURE-----