[debian-mysql] Bug#1009290: mariadb-server-10.6: Fails to start on live system

[Witold Baryluk]

Package: mariadb-server
Version: 1:10.11.3-1
Followup-For: Bug #1009290
X-Debbugs-Cc: witold.baryluk at gmail.com

Just wwitching to fsync, does not appear to solve the problem either:

root at debian:~# cat  /etc/mysql/mariadb.conf.d/90-live.cnf
[mysqld]
innodb_flush_method = fsync
root at debian:~# 

Jun 25 23:30:03 debian systemd[1]: Starting mariadb.service - MariaDB 10.11.3 database server...
Jun 25 23:30:03 debian mariadbd[1395434]: 2023-06-25 23:30:03 0 [Note] Starting MariaDB 10.11.3-MariaDB-1 source revision  as process 1395434
Jun 25 23:30:03 debian mariadbd[1395434]: 2023-06-25 23:30:03 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
Jun 25 23:30:03 debian mariadbd[1395434]: 2023-06-25 23:30:03 0 [Note] InnoDB: Number of transaction pools: 1
Jun 25 23:30:03 debian mariadbd[1395434]: 2023-06-25 23:30:03 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
Jun 25 23:30:03 debian mariadbd[1395434]: 2023-06-25 23:30:03 0 [Note] InnoDB: Using liburing
Jun 25 23:30:03 debian mariadbd[1395434]: 2023-06-25 23:30:03 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
Jun 25 23:30:03 debian mariadbd[1395434]: 2023-06-25 23:30:03 0 [Note] InnoDB: Completed initialization of buffer pool
Jun 25 23:30:03 debian mariadbd[1395434]: 2023-06-25 23:30:03 0 [ERROR] InnoDB: The Auto-extending data file './ibdata1' is of a different size 0 pages than specified by innodb_data_file_path
Jun 25 23:30:03 debian mariadbd[1395434]: 2023-06-25 23:30:03 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
Jun 25 23:30:03 debian mariadbd[1395434]: 2023-06-25 23:30:03 0 [Note] InnoDB: Starting shutdown...
Jun 25 23:30:03 debian mariadbd[1395434]: 2023-06-25 23:30:03 0 [ERROR] Plugin 'InnoDB' init function returned error.
Jun 25 23:30:03 debian mariadbd[1395434]: 2023-06-25 23:30:03 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Jun 25 23:30:03 debian mariadbd[1395434]: 2023-06-25 23:30:03 0 [Note] Plugin 'FEEDBACK' is disabled.
Jun 25 23:30:03 debian mariadbd[1395434]: 2023-06-25 23:30:03 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some plugins may be not loaded
Jun 25 23:30:03 debian mariadbd[1395434]: 2023-06-25 23:30:03 0 [ERROR] Unknown/unsupported storage engine: InnoDB
Jun 25 23:30:03 debian mariadbd[1395434]: 2023-06-25 23:30:03 0 [ERROR] Aborting
Jun 25 23:30:03 debian systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jun 25 23:30:03 debian systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jun 25 23:30:03 debian systemd[1]: Failed to start mariadb.service - MariaDB 10.11.3 database server.


This is probably, becuase postinst script probably (silently) failed, and
something was not initialized properly during install.

Adding runtime check in that script to detect overlay fs will not be
enough, because it is possible to install mariadb-server in chroot for
live image, which could be on non-overlay fs, but when actually started
it might be on overlay fs.

It would be preferable to do this in startup script instead, but then a
lot of logic would probably need to move from postinst, to startup script.