hi there
Since i upgraded our MySQL version to 8.0.29 the backup with xtrabackup is failing due to a corrupt log record.
Error in log:
2022-05-05T14:57:45.023045+02:00 0 [Note] [MY-012522] [InnoDB] Set innodb_force_recovery to ignore this error.
2022-05-05T14:57:45.023064+02:00 0 [ERROR] [MY-012519] [InnoDB] ############### CORRUPT LOG RECORD FOUND ###############
2022-05-05T14:57:45.023077+02:00 0 [Note] [MY-012520] [InnoDB] Log record type 67, page 201:1492. Log parsing proceeded successfully up to 59650859782. Previous log record type 67, is multi 0 Recv offset 219, prev 219
2022-05-05T14:57:45.023089+02:00 0 [Note] [MY-012521] [InnoDB] Hex dump starting 100 bytes before and ending 100 bytes after the corrupted record:
len 200; hex 1fe1001f8800053e24000062936a18fbee81a9000062936a02fbee81a90028811002fbee81a9002a811002fbee81a9006881101f94fbee81a900290b00854f2465373338663331392d663833302d343730382d393332612d656562346635613561663834c380c985d400010009000180008006800780000000000500057fff80002ccf8107000a00081c242407000208f39265373338663331392d663833302d343730382d393332612d65656234663561356166383400000062936a82000001a901103336363262; asc >$ b j b j ( * h ) O$e738f319-f830-4708-932a-eeb4f5a5af84 , $$ e738f319-f830-4708-932a-eeb4f5a5af84 b j 3662b;
Is there any known issues with these version? I just read the https://www.percona.com/blog/quick-peek-at-mysql-8-0-29/ where is says there is no big change in this version. But still i do have the issue since the upgrade of MySQL.
I also found a similiar ticket with the same error message with version 8.0.22 here: https://jira.percona.com/browse/PXB-2319
BR Lukas