Mariadb-backup 10.11.9 crash

2025-01-24 12:28:30 0x7f2cf53b9640 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.11.9/extra/mariabackup/xtrabackup.cc line 1218
InnoDB: Failing assertion: opt_no_lock
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 mariadbd 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.
250124 12:28:30 [ERROR] mysqld got signal 6 ;
Sorry, we probably made a mistake, and this is a bug.

Your assistance in bug reporting will enable us to fix this for the next release.
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.11.9-MariaDB source revision: 0e8fb977b00983d98c4c35e39bc1f36463095938
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 = 6239 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
/usr//bin/mariadb-backup(my_print_stacktrace+0x2e)[0x55c7aa0d332e]
/usr//bin/mariadb-backup(handle_fatal_signal+0x478)[0x55c7a9bdd428]
/lib64/libc.so.6(+0x3e730)[0x7f2cf723e730]
/lib64/libc.so.6(+0x8bacc)[0x7f2cf728bacc]
/lib64/libc.so.6(raise+0x16)[0x7f2cf723e686]
/lib64/libc.so.6(abort+0xd3)[0x7f2cf7228833]
/usr//bin/mariadb-backup(+0x6e52e4)[0x55c7a977d2e4]
/usr//bin/mariadb-backup(+0x682a56)[0x55c7a971aa56]
/usr//bin/mariadb-backup(+0xebe305)[0x55c7a9f56305]
/usr//bin/mariadb-backup(+0xebe7f2)[0x55c7a9f567f2]
/usr//bin/mariadb-backup(+0x73e83e)[0x55c7a97d683e]
/usr//bin/mariadb-backup(+0x73eb6f)[0x55c7a97d6b6f]
/lib64/libstdc++.so.6(+0xdbad4)[0x7f2cf76dbad4]
/lib64/libc.so.6(+0x89d82)[0x7f2cf7289d82]
/lib64/libc.so.6(+0x10ee20)[0x7f2cf730ee20]
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /var/lib/mysql/db
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 unlimited unlimited bytes
Max resident set unlimited unlimited bytes
Max processes 769724 769724 processes
Max open files 32768 32768 files
Max locked memory unlimited unlimited bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 769724 769724 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

Kernel version: Linux version 5.14.0-511.el9.x86_64 (mockbuild@x86-05.stream.rdu2.redhat.com) (gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2), GNU ld version 2.35.2-54.el9) #1 SMP PREEMPT_DYNAMIC Thu Sep 19 06:52:39 UTC 2024