Am 16.10.19 um 11:29 schrieb Gordan Bobic: > On Wed, Oct 16, 2019 at 10:17 AM Reindl Harald <h.rei...@thelounge.net > <mailto:h.rei...@thelounge.net>> wrote: > > > Am 16.10.19 um 10:23 schrieb Gordan Bobic: > > I don't know if it is recoverable but it sounds like you missed > the step > > of always needing a full, clean shutdown between upgrades with > > innodb_fast_shutdown=0. Then you can delete ib_logfile*, and upgrade. > > always? > > > Yes.
nonsense > how comes that i didn't need that for the whole past decade which means > MySQl 5.0 to MariaDB 10.3 and frankly i wouldn't expect it at all, this > is not PostgreSQL > > Short of an incredible amount of luck, resulting in the ib_logfiles > being completely flushed at the point of shutdown (or you having > innodb_fast_shutdown=0 set in your configs), no, i don't > I don't have an explanation > for why for you. I have never seen an upgrade from MariaDB 10.1 and > earlier to MariaDB 10.2 and later work without following the described > process, and I have carried out dozens of such upgrades over the last > few years. maybe just don't jump on early releases as fast as you can helps a lot, see below > It is documented, and a simple yum update specifically refuses to > upgrade the MariaDB-server package for this exact reason. You have to do > a clean shutdown, manually remove the old MariaDB-server package and > then install the new MariaDB-server package. https://mariadb.com/kb/en/library/upgrading-from-mariadb-101-to-mariadb-102/ Set innodb_fast_shutdown to 0. It can be changed dynamically with SET GLOBAL. For example: SET GLOBAL innodb_fast_shutdown=0; This step is not necessary when upgrading to MariaDB 10.2.5 or later. Omitting it can make the upgrade process far faster. See MDEV-12289 for more information. _______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
