HELP!
after I Upgrade mysql from 5.6.28 to 8.0.23,i used percona-xtrabackup-8.0.23-16 to backup mysql8.0.23’s data, but an error occurred when use the --prepare command with percona-xtrabackup-8.0.23-16,the error message is
InnoDB: Assertion failure: os0file.cc:2907
InnoDB: thread 140477846411648InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.percona.com/projects/PXB.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: MySQL :: MySQL 8.0 Reference Manual :: 15.21.3 Forcing InnoDB Recovery
InnoDB: about forcing recovery.
07:03:37 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong…
stack_bottom = 0 thread_stack 0x46000
/tmp/percona-xtrabackup-8.0.23-16-Linux-x86_64.glibc2.12-minimal/bin/xtrabackup(my_print_stacktrace(unsigned char const*, unsigned long)+0x2e) [0x23d14ce]
/tmp/percona-xtrabackup-8.0.23-16-Linux-x86_64.glibc2.12-minimal/bin/xtrabackup(handle_fatal_signal+0x2f3) [0x1205733]
/lib64/libpthread.so.0(+0xf630) [0x7fc38be11630]
/lib64/libc.so.6(gsignal+0x37) [0x7fc389c0a3d7]
/lib64/libc.so.6(abort+0x148) [0x7fc389c0bac8]
/tmp/percona-xtrabackup-8.0.23-16-Linux-x86_64.glibc2.12-minimal/bin/xtrabackup(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0xb2) [0x1686402]
/tmp/percona-xtrabackup-8.0.23-16-Linux-x86_64.glibc2.12-minimal/bin/xtrabackup(os_file_flush_func(int)+0x93) [0x155b483]
/tmp/percona-xtrabackup-8.0.23-16-Linux-x86_64.glibc2.12-minimal/bin/xtrabackup(os_file_set_size(char const*, pfs_os_file_t, unsigned long, unsigned long, bool, bool)+0x728) [0x1564638]
/tmp/percona-xtrabackup-8.0.23-16-Linux-x86_64.glibc2.12-minimal/bin/xtrabackup() [0xca525a]
/tmp/percona-xtrabackup-8.0.23-16-Linux-x86_64.glibc2.12-minimal/bin/xtrabackup() [0xca559b]
/tmp/percona-xtrabackup-8.0.23-16-Linux-x86_64.glibc2.12-minimal/bin/xtrabackup(srv_start(bool, unsigned long)+0x1a70) [0x16314a0]
/tmp/percona-xtrabackup-8.0.23-16-Linux-x86_64.glibc2.12-minimal/bin/xtrabackup() [0xcecd8b]
/tmp/percona-xtrabackup-8.0.23-16-Linux-x86_64.glibc2.12-minimal/bin/xtrabackup() [0xceeba9]
/tmp/percona-xtrabackup-8.0.23-16-Linux-x86_64.glibc2.12-minimal/bin/xtrabackup(main+0xca9) [0xcab749]
/lib64/libc.so.6(__libc_start_main+0xf5) [0x7fc389bf6555]
/tmp/percona-xtrabackup-8.0.23-16-Linux-x86_64.glibc2.12-minimal/bin/xtrabackup() [0xcda599]
I want to sure if there is a bug that percona-xtrabackup-8.0.23-16 could’t be used with mysql8.0.23 version ,if this mysql 8.0.23 version was upgraded from other versions