Comments - Why its mysqld error occurs during Mariabackup

Hi,

I have exactly the same problem :

[00] 2020-10-12 15:07:13 >> log scanned up to (1356320866675)
[00] 2020-10-12 15:07:14 >> log scanned up to (1356320866675)
[00] 2020-10-12 15:07:15 >> log scanned up to (1356320866675)
[00] 2020-10-12 15:07:16 >> log scanned up to (1356320866675)
[00] 2020-10-12 15:07:17 >> log scanned up to (1356320866675)
[00] 2020-10-12 15:07:18 >> log scanned up to (1356320866675)
[00] 2020-10-12 15:07:19 >> log scanned up to (1356320866675)
[00] 2020-10-12 15:07:20 >> log scanned up to (1356320866675)
[00] 2020-10-12 15:07:21 >> log scanned up to (1356320866675)
[00] 2020-10-12 15:07:22 >> log scanned up to (1356320866675)
[00] 2020-10-12 15:07:23 >> log scanned up to (1356320866675)
[00] 2020-10-12 15:07:24 >> log scanned up to (1356320866675)
2020-10-12 15:07:25 0 [Note] InnoDB: Read redo log up to LSN=1356320866816
[00] 2020-10-12 15:07:25 >> log scanned up to (1356320866675)
[00] 2020-10-12 15:07:26 >> log scanned up to (1356320866675)
[00] 2020-10-12 15:07:27 >> log scanned up to (1356320866675)
[00] 2020-10-12 15:07:28 >> log scanned up to (1356320866675)
[00] 2020-10-12 15:07:29 >> log scanned up to (1356320866675)
[00] 2020-10-12 15:07:30 >> log scanned up to (1356320866675)
[00] 2020-10-12 15:07:31 >> log scanned up to (1356320866675)
[00] 2020-10-12 15:07:32 >> log scanned up to (1356320866675)
[00] 2020-10-12 15:07:33 >> log scanned up to (1356320866675)
Assertion "(to_read & (page_size - 1)) == 0" failed at /build/mariadb-10.3-V9JMsi/mariadb-10.3-10.3.23/extra/mariabackup/fil_cur.cc:421                     
201012 15:07:33 [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.23-MariaDB-0+deb10u1
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 = 5599 K  bytes of memory                                                               
Hope that's ok; if not, decrease some variables in the equation.

I have tested mariabackup on another serveur, with the same mysql databases and the same settings, mariabackup run correctly.

Do you have an idea to work around this problem ?