Comments - Mariadb crashed during deleting a database
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
MariaDB 10.2.31 was released in January 2020. The last release in that series was MariaDB 10.2.44, which was released in May 2022. The last release that uses a compatible InnoDB log format is MariaDB 10.4.34 (May 2024).
The messages "log sequence number is in the future" are very serious, indicating that the write-ahead logging was broken and that the database pages are in an inconsistent state with respect to each other, that is, some pages correspond to an unexpectedly new logical time. You can expect such trouble when renaming or removing the log files. MDEV-27199 in a later major version introduced some safeguards against this.
In MariaDB 10.6, several fixes were applied so that InnoDB should not crash when encountering corruption. The version that you are using does include a fix of MDEV-21069, which should avoid some crashes when dropping a corrupted table.
I believe that your best option is to hope that the server will not crash when executing
mysqldump, and to load that dump to MariaDB 10.6 or MariaDB 10.11.Thank you for your reply.
wow! You're saying things I was hoping not to hear already.
mysqldump threw an error as well: mysqldump: Got error: 2002: "Can't connect to local MySQL server through socket '/run/mysql/mysql.sock' (111)" when trying to connect
There's got to be a way to connect and dump the (10 good databases for 3 sites!) databases on mariadb.
What else can be done?
Try to start an 10.4 server on a copy of the data and take the dump from there.
per InnoDB Redo Log Directly editing or moving the redo logs can cause corruption, and should never normally be attempted.
Thanks for your reply.
" per InnoDB Redo Log Directly editing or moving the redo logs can cause corruption, and should never normally be attempted." Thank you, well noted.
"start an 10.4 server on a copy of the data" I'm not sure I quite understand what you meant. Do you mean to install 10.4 and then use database backup?
Note: Only mariadb 10.2 came packaged with openSUSE Leap 15.1. I am not sure of 10.4 compatibility with openSUSE Leap 15.1.