MySQL Forums
Forum List  »  InnoDB

Re: Failed to start mysql due to start_lsn and ens_lsn issue
Posted by: Hanru Jacobs
Date: August 10, 2022 07:58AM

Thank you for explaining the performance_schema.innodb_redo_log_files table, I though it might have been something like that but could not get any info.

As I mentioned before it looks like all the data is there in the DB. Is it not possible to reset the counters on innodb and just start the innodb from scratch? Just removing the files does not have the desired result as the DB still knows about the #ib_redo#### files that is supposed to be in the var/lib/mysql/#innodb_redo# directory and does not boot. Is there no way that I can tell mysql to just start innodb from fresh?

>(Alternatively: perhaps you've recovered the files from some inconsistent snapshot)
No I did not the DB was running fine before the power failure and I did not try to recover from any medium. I guess you might be referring to a Virtual Machine. It is running on the metal and not a VM.

>Q1. Can you share some more details about your LVM configuration?
Here you go, hope it what you need. If not just let me know.

LVM version: 2.03.11(2) (2021-01-08)
Library version: 1.02.175 (2021-01-08)
Driver version: 4.45.0
Configuration: ./configure --build=x86_64-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-option-checking --disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu --runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking --libdir=/lib/x86_64-linux-gnu --sbindir=/sbin --with-usrlibdir=/usr/lib/x86_64-linux-gnu --with-optimisation=-O2 --with-cache=internal --with-device-uid=0 --with-device-gid=6 --with-device-mode=0660 --with-default-pid-dir=/run --with-default-run-dir=/run/lvm --with-default-locking-dir=/run/lock/lvm --with-thin=internal --with-thin-check=/usr/sbin/thin_check --with-thin-dump=/usr/sbin/thin_dump --with-thin-repair=/usr/sbin/thin_repair --with-udev-prefix=/ --enable-applib --enable-blkid_wiping --enable-cmdlib --enable-dmeventd --enable-editline --enable-lvmlockd-dlm --enable-lvmlockd-sanlock --enable-lvmpolld --enable-notify-dbus --enable-pkgconfig --enable-udev_rules --enable-udev_sync --disable-readline
###@###:/var/lib/mysql/#innodb_redo# vgdisplay
--- Volume group ---
VG Name ubuntu-vg
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 5
VG Access read/write
VG Status resizable
Cur LV 1
Open LV 1
Max PV 0
Cur PV 1
Act PV 1
VG Size <2.73 TiB
PE Size 4.00 MiB
Total PE 714495
Alloc PE / Size 714495 / <2.73 TiB
Free PE / Size 0 / 0
VG UUID 3kIRs7-####-####-MYs0-8ZXq-####-fQKqi8

--- Logical volume ---
LV Path /dev/ubuntu-vg/ubuntu-lv
LV Name ubuntu-lv
VG Name ubuntu-vg
LV UUID 17cg2C-####-####-PSij-####-####-1BoQ9Z
LV Write Access read/write
LV Creation host, time ubuntu-server, 2022-06-13 19:32:57 +0000
LV Status available
# open 1
LV Size <2.73 TiB
Current LE 714495
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0

Options: ReplyQuote

Written By
Re: Failed to start mysql due to start_lsn and ens_lsn issue
August 10, 2022 07:58AM

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.