MariaBackup failed, while percona-xtrabackup works

170705 10:04:07 Connecting to MySQL server host: 127.0.0.1, user: backup, password: set, port: 3306, socket: not set
Using server version 10.1.25-MariaDB
mariabackup based on MariaDB server 10.1.25-MariaDB Linux (x86_64)
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /opt/mysql/
xtrabackup: open files limit requested 65535, set to 100001
xtrabackup: using the following InnoDB configuration:
xtrabackup: innodb_data_home_dir = /opt/mysql
xtrabackup: innodb_data_file_path = ibdata1:128M:autoextend
xtrabackup: innodb_log_group_home_dir = /opt/mysql
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 268435456
2017-07-05 10:04:07 7f6e2bba9900 InnoDB: Using Linux native AIO
xtrabackup: using O_DIRECT
xtrabackupp: Warning: ignoring innodb_flush_method = O_DIRECT on Windows.
170705 10:04:07 >> log scanned up to (376193374)
2017-07-05 10:04:07 7f6e2bba9900 InnoDB: Assertion failure in thread 140111156779264 in file srv0start.cc line 1511
InnoDB: Failing assertion: prev_space_id + 1 == undo_tablespace_ids[i]
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
170705 10:04:07 [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.1.25-MariaDB
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 = 5301 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 0x48400
addr2line: 'mariabackup': No such file
mariabackup(my_print_stacktrace+0x2e)[0x7f6e2c6b308e]
mariabackup(handle_fatal_signal+0x305)[0x7f6e2c1dd2f5]
/lib64/libpthread.so.0(+0xf370)[0x7f6e2b7bf370]
/lib64/libc.so.6(gsignal+0x37)[0x7f6e29b141d7]
/lib64/libc.so.6(abort+0x148)[0x7f6e29b158c8]
mariabackup(+0x8eed9b)[0x7f6e2c4ddd9b]
mariabackup(+0x3a6edc)[0x7f6e2bf95edc]
mariabackup(_Z22xtrabackup_backup_funcv+0xc5d)[0x7f6e2bf9bcdd]
mariabackup(main+0xd31)[0x7f6e2bf7bed1]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f6e29b00b35]
mariabackup(+0x3a559d)[0x7f6e2bf9459d]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

mariabackup cmd
#mariabackup --defaults-file=/etc/my.cnf --backup --compress --host=127.0.0.1 --port=3306 --user=backup --password=changeme --compress-threads=8 --parallel=4 --extra-lsndir=/var/local-backup --stream=xbstream --tmpdir=/tmp/backup_3306 --target-dir=/var/local-backup 2>>/var/tmp/backup_3306.log | ssh -p 222 root@127.0.0.1 "cat - > /opt/backup/databases/backup_2017_07_05_08_00.xbs"

innobackupex cmd
#innobackupex --compress --host=127.0.0.1 --port=3306 --user=backup --password=changeme --compress-threads=8 --parallel=4 --extra-lsndir=/var/local-backup --stream=xbstream --tmpdir=/tmp/backup_3306 /var/local-backup 2>> /var/tmp/backup_3306.log | ssh -p 222 root@127.0.0.1 "cat - > /opt/backup/databases/backup_2017_07_05_10_05.xbs"