Preparring backup restoration

mariabackup --prepare --target-dir=/root/xtrabackup_backupfiles/
mariabackup based on MariaDB server 10.3.39-MariaDB Linux (x86_64)
[00] 2023-10-23 13:50:46 cd to /root/xtrabackup_backupfiles/
[00] 2023-10-23 13:50:46 open files limit requested 0, set to 1024
[00] 2023-10-23 13:50:46 This target seems to be already prepared.
[00] 2023-10-23 13:50:46 mariabackup: using the following InnoDB configuration for recovery:
[00] 2023-10-23 13:50:46 innodb_data_home_dir = .
[00] 2023-10-23 13:50:46 innodb_data_file_path = ibdata1:12M:autoextend
[00] 2023-10-23 13:50:46 innodb_log_group_home_dir = .
[00] 2023-10-23 13:50:46 InnoDB: Using Linux native AIO
[00] 2023-10-23 13:50:46 Starting InnoDB instance for recovery.
[00] 2023-10-23 13:50:46 mariabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
2023-10-23 13:50:46 0 [Note] InnoDB: The first innodb_system data file 'ibdata1' did not exist. A new tablespace will be created!
2023-10-23 13:50:46 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-10-23 13:50:46 0 [Note] InnoDB: Uses event mutexes
2023-10-23 13:50:46 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023-10-23 13:50:46 0 [Note] InnoDB: Number of pools: 1
2023-10-23 13:50:46 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-10-23 13:50:46 0 [Note] InnoDB: Initializing buffer pool, total size = 100M, instances = 1, chunk size = 100M
2023-10-23 13:50:46 0 [Note] InnoDB: Completed initialization of buffer pool
2023-10-23 13:50:46 0 [Note] InnoDB: page_cleaner coordinator priority: -20
2023-10-23 13:50:46 0 [Note] InnoDB: Setting file './ibdata1' size to 12 MB. Physically writing the file full; Please wait ...
2023-10-23 13:50:46 0 [Note] InnoDB: File './ibdata1' size is now 12 MB.
2023-10-23 13:50:46 0 [Note] InnoDB: Setting log file ./ib_logfile101 size to 50331648 bytes
2023-10-23 13:50:46 0 [Note] InnoDB: Setting log file ./ib_logfile1 size to 50331648 bytes
2023-10-23 13:50:46 0x7f4d8c52f940 InnoDB: Assertion failure in file /builddir/build/BUILD/mariadb-10.3.39/storage/innobase/srv/srv0start.cc line 807
InnoDB: Failing assertion: !create_new_db || srv_operation == SRV_OPERATION_NORMAL
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
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: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
231023 13:50:46 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.3.39-MariaDB source revision: ca001cf2048f0152689e1895e2dc15486dd0b1af
key_buffer_size=0
read_buffer_size=131072
max_used_connections=0
max_threads=1
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 5611 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

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 = 0x0 thread_stack 0x49000
mariabackup(my_print_stacktrace+0x41)[0x5636a209d251]
mariabackup(handle_fatal_signal+0x4f5)[0x5636a1c23225]
/lib64/libpthread.so.0(+0x12c20)[0x7f4d8a255c20]
/lib64/libc.so.6(gsignal+0x10f)[0x7f4d89eb537f]
/lib64/libc.so.6(abort+0x127)[0x7f4d89e9fdb5]
mariabackup(+0x50f233)[0x5636a18db233]
mariabackup(+0x507356)[0x5636a18d3356]
mariabackup(+0x508a06)[0x5636a18d4a06]
mariabackup(+0x53a6ab)[0x5636a19066ab]
mariabackup(main+0x19d)[0x5636a18e3cad]
/lib64/libc.so.6(__libc_start_main+0xf3)[0x7f4d89ea1493]
mariabackup(_start+0x2e)[0x5636a18f7d6e]
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /root/xtrabackup_backupfiles
Resource Limits:
Limit Soft Limit Hard Limit Units
Max cpu time unlimited unlimited seconds
Max file size unlimited unlimited bytes
Max data size unlimited unlimited bytes
Max stack size 8388608 unlimited bytes
Max core file size 0 unlimited bytes
Max resident set unlimited unlimited bytes
Max processes 14800 14800 processes
Max open files 1024 262144 files
Max locked memory 65536 65536 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 14800 14800 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 0 0
Max realtime timeout unlimited unlimited us
Core pattern: |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %e

Kernel version: Linux version 4.18.0-348.el8.0.2.x86_64 (mockbuild@dal1-prod-builder001.bld.equ.rockylinux.org) (gcc version 8.5.0 20210514 (Red Hat 8.5.0-3) (GCC)) #1 SMP Sun Nov 14 00:51:12 UTC 2021

Aborted (core dumped)