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

2021-10-22 Thread Yves-Alexis Perez
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2021-10-22 at 15:22 +0200, Ondrej Zary wrote: > With 10.3.29 running, I've dumped all databases (mysqldump --all-databases - > p >mysql.dump), then dropped all databases, stopped mariadb and deleted > /var/lib/mysql/ib*. > Then restarted

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

2021-10-22 Thread Ondrej Zary
On Friday 22 October 2021, Yves-Alexis Perez wrote: > On Thu, 2021-10-14 at 19:38 +0200, Ondrej Zary wrote: > >     MDEV-15912: Remove traces of insert_undo > > > >     Let us simply refuse an upgrade from earlier versions if the > >     upgrade procedure was not followed. This simplifies the

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

2021-10-22 Thread Yves-Alexis Perez
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, 2021-10-14 at 19:38 +0200, Ondrej Zary wrote: >     MDEV-15912: Remove traces of insert_undo > >     Let us simply refuse an upgrade from earlier versions if the >     upgrade procedure was not followed. This simplifies the purge, >    

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

2021-10-14 Thread Ondrej Zary
e46f76c9749d7758765ba274a212cfc2dcf3eeb8 is the first bad commit commit e46f76c9749d7758765ba274a212cfc2dcf3eeb8 Author: Marko Mäkelä Date: Mon Jun 21 12:34:07 2021 +0300 MDEV-15912: Remove traces of insert_undo Let us simply refuse an upgrade from earlier versions if the upgrade

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

2021-10-14 Thread Ondrej Zary
Tested upstream mariadb packages. 10.3.30 works, 10.3.31 fails. -- Ondrej Zary

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

2021-10-14 Thread 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 > >

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

2021-10-14 Thread Otto Kekäläinen
> 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. Run it with the old database, make a logical dump (with mysqldump) and import that logical dump into a

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

2021-10-14 Thread Yves-Alexis Perez
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 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 >

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

2021-10-14 Thread Otto Kekäläinen
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

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

2021-10-14 Thread Yves-Alexis Perez
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2021-10-13 at 19:06 -0700, Otto Kekäläinen wrote: > I added this patch to the packaging in > https://salsa.debian.org/mariadb-team/mariadb-10.5/-/commit/2a8f83531a2ff22a31c61b8bef28dabf77b25b78 > and once the CI completes (if it runs without

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

2021-10-13 Thread Otto Kekäläinen
Hello! On Tue, Oct 12, 2021 at 4:51 AM Yves-Alexis Perez wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Mon, 2021-10-11 at 11:27 +0200, Jan Korbel wrote: > > Maybe this: https://bugs.freebsd.org/bugzilla//show_bug.cgi?id=257728 > > If I read the bug correctly, it points to >