MySQL Forums
Forum List  »  InnoDB

Re: Failed to start mysql due to start_lsn and ens_lsn issue
Posted by: Peter Brawley
Date: August 05, 2022 08:33AM

8.0.30 seems to have radically changed redo log implementation (ib_logfile0 and ib_logfile1) with a much more complex (not to mention opaque) file arrangement. Now, redo log files use an #ib_redoN naming convention, where N is the redo log file number, and a blizzard of new configuration variables controls the new implementation (https://dev.mysql.com/doc/refman/8.0/en/innodb-redo-log.html#innodb-modifying-redo-log-capacity).

Before 8.0.30, we could just move ib_logfile* to another folder and MySQL would rebuild them automatically. I don't know if there's an equivalent possibility in 8.0.30. If there are any such files present, you could move them to another location and see if they get rebuilt.

And, do you have a backup from before the crash?



Edited 1 time(s). Last edit at 08/05/2022 08:36AM by Peter Brawley.

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: Failed to start mysql due to start_lsn and ens_lsn issue
147
August 05, 2022 08:33AM


Sorry, only registered users may post in this forum.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.