#2571 Issue closed
: rear mkbackup ERROR: rsync failed with return code 23¶
Labels: support / question
, not ReaR / invalid
ryanlindsay opened issue at 2021-02-18 05:00:¶
-
ReaR version ("/usr/sbin/rear -V"): 2.4
-
OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"): Centos 7
-
ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
# Our packages will never ship with a site.conf.
BACKUP=NETFS
BACKUP_PROG=rsync
BACKUP_PROG_OPTIONS+=(-av)
#BACKUP_PROG_OPTIONS+=( --xattrs --xattrs-include ='*.*' )
BACKUP_PROG_EXCLUDE = /spare/* /home/* /data/* /bioinf_core/* /physical_sciences/* /pipeline/* /tmp/* /dev/shm/* /config/* *.cache
BACKUP_URL=sshfs://rear@vmdv-res-utils/config/backup/rear/
OUTPUT=ISO
OUTPUT_URL=sshfs://rear@vmdv-res-utils/config/backup/rear/
-
Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR): Hardware
-
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device): x86
-
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot): GRUB
-
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe): SSD
-
Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,SIZE,MOUNTPOINT" or "lsblk" as makeshift):
-
Description of the issue (ideally so that others can reproduce it):
When I run rear -v mkbackup. Making the iso works.
The backup via rsync looks like it's working then it errors out with
2021-02-18 14:19:03.653412618 ======================
2021-02-18 14:19:03.662040555 Including backup/default/005_valid_backup_methods.sh
2021-02-18 14:19:03.673537567 Including backup/default/010_pre_backup_script.sh
2021-02-18 14:19:03.678362962 Including backup/NETFS/default/100_mount_NETFS_path.sh
mkdir: created directory '/tmp/rear.vJp4DxNF5QPAuDP/outputfs'
2021-02-18 14:19:03.690232283 Mounting with 'sshfs rear@vmdv-res-utils:/config/backup/rear/ /tmp/rear.vJp4DxNF5QPAuDP/outputfs -o rw,noatime'
2021-02-18 14:19:03.898623872 Including backup/NETFS/default/150_save_copy_of_prefix_dir.sh
2021-02-18 14:19:03.903468855 Including backup/NETFS/default/200_check_rsync_relative_option.sh
2021-02-18 14:19:03.907738090 Added option '--relative' to the BACKUP_RSYNC_OPTIONS array during mkbackup workflow
2021-02-18 14:19:03.912822015 Including backup/NETFS/default/200_make_prefix_dir.sh
2021-02-18 14:19:03.926344235 Including backup/NETFS/default/250_create_lock.sh
2021-02-18 14:19:03.941487712 Including backup/NETFS/GNU/Linux/310_stop_selinux.sh
2021-02-18 14:19:03.946303035 Including backup/NETFS/default/400_create_include_exclude_files.sh
2021-02-18 14:19:03.952002846 Including backup/NETFS/default/500_make_backup.sh
2021-02-18 14:19:03.953707735 Include list:
2021-02-18 14:19:03.955589238 /var/log/audit
2021-02-18 14:19:03.957378465 /var/log
2021-02-18 14:19:03.959179148 /
2021-02-18 14:19:03.961008312 /tmp
2021-02-18 14:19:03.962795582 /var
2021-02-18 14:19:03.964600204 /boot
2021-02-18 14:19:03.966379669 Exclude list:
2021-02-18 14:19:03.968187798 /tmp/*
2021-02-18 14:19:03.969953434 /dev/shm/*
2021-02-18 14:19:03.971716534 /var/lib/rear/output/*
2021-02-18 14:19:03.973469104 /tmp/rear.vJp4DxNF5QPAuDP
2021-02-18 14:19:03.981041409 Encrypting backup archive is disabled
2021-02-18 14:19:03.982993976 Creating rsync archive '/tmp/rear.vJp4DxNF5QPAuDP/outputfs/papr-res-compute206/backup'
2021-02-18 15:14:40.724413797 ERROR: rsync failed with return code 23
This means that the archiving process ended prematurely, or did
not even start. As a result it is unlikely you can recover this
system properly. Relax-and-Recover is therefore aborting execution.
==== Stack trace ====
Trace 0: /usr/sbin/rear:547 main
Trace 1: /usr/share/rear/lib/mkbackup-workflow.sh:26 WORKFLOW_mkbackup
Trace 2: /usr/share/rear/lib/framework-functions.sh:101 SourceStage
Trace 3: /usr/share/rear/lib/framework-functions.sh:49 Source
Trace 4: /usr/share/rear/backup/NETFS/default/500_make_backup.sh:263 source
Message: rsync failed with return code 23
This means that the archiving process ended prematurely, or did
not even start. As a result it is unlikely you can recover this
system properly. Relax-and-Recover is therefore aborting execution.
== End stack trace ==
-
Workaround, if any:
-
Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):
To paste verbatim text like command output or file content,
include it between a leading and a closing line of three backticks like
```
verbatim content
```
gdha commented at 2021-02-18 08:00:¶
That is a permission issue - not an error of ReaR, but coming from rsync
- see:
https://programmerah.com/solution-rsync-error-some-files-could-not-be-transferred-code-23-at-main-c-702-10011/
[Export of Github issue for rear/rear.]