#3630 Issue closed: rear mkbackup failing due to failing_backup_prog: No such file or directory¶
Labels: fixed / solved / done, minor bug
gdha opened issue at 2026-08-31 12:58:¶
ReaR version¶
rear-2.6-28.el9.x86_64
Describe the ReaR bug in detail¶
A couple of weeks one system always exits with the following error:
2026-08-25 03:52:26.019764260 Including backup/NETFS/default/500_make_backup.sh
...
2026-08-25 03:52:26.159270745 /var/tmp/rear.iQqEW8TVxvtbXCo
2026-08-25 03:52:26.161290667 Creating tar archive '/var/tmp/rear.iQqEW8TVxvtbXCo/outputfs/image/backup.tar.zst'
2026-08-25 03:52:26.173433633 tar --warning=no-xdev --sparse --block-number --totals --verbose --no-wildcards-match-slash --one-file-system --ignore-failed-read --anchored --xattrs --xattrs-include=security.capability --xattrs-include=security.selinux --acls --use-compress-program=zstd -X /var/tmp/rear.iQqEW8TVxvtbXCo/tmp/backup-exclude.txt -C / -c -f - /var/log/audit /home /var/log /opt / /opt/Tanium /tmp /usr /var /var/lib/rancher /app/util /boot /var/log/rear/rear-OPCITSEUL00H9.log | dd of=/var/tmp/rear.iQqEW8TVxvtbXCo/outputfs/image/backup.tar.zst bs=1M
cat: /var/tmp/rear.iQqEW8TVxvtbXCo/tmp/failing_backup_prog: No such file or directory
cat: /var/tmp/rear.iQqEW8TVxvtbXCo/tmp/failing_backup_prog_rc: No such file or directory
2026-08-25 03:55:09.524891496 ERROR: failed with return code and below output:
---snip---
----------
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:568 main
Trace 1: /usr/share/rear/lib/mkbackup-workflow.sh:26 WORKFLOW_mkbackup
Trace 2: /usr/share/rear/lib/framework-functions.sh:116 SourceStage
Trace 3: /usr/share/rear/lib/framework-functions.sh:56 Source
Platform¶
Linux x64
OS version¶
RHEL 9.8
Backup¶
NETFS
Storage layout¶
$ lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,LABEL,SIZE,MOUNTPOINT
NAME KNAME PKNAME TRAN TYPE FSTYPE LABEL SIZE MOUNTPOINT
/dev/sda /dev/sda disk 64G
|-/dev/sda1 /dev/sda1 /dev/sda part xfs 1G /boot
`-/dev/sda2 /dev/sda2 /dev/sda part LVM2_member 63G
|-/dev/mapper/vg00-lv_root /dev/dm-0 /dev/sda2 lvm xfs 4G /
|-/dev/mapper/vg00-lv_swap /dev/dm-1 /dev/sda2 lvm swap 3.7G [SWAP]
|-/dev/mapper/vg00-lv_usr /dev/dm-2 /dev/sda2 lvm xfs 5G /usr
|-/dev/mapper/vg00-lv_opt /dev/dm-5 /dev/sda2 lvm xfs 5G /opt
|-/dev/mapper/vg00-lv_audit /dev/dm-6 /dev/sda2 lvm xfs 6G /var/log/audit
|-/dev/mapper/vg00-lv_log /dev/dm-7 /dev/sda2 lvm xfs 7G /var/log
|-/dev/mapper/vg00-lv_var /dev/dm-8 /dev/sda2 lvm xfs 8G /var
|-/dev/mapper/vg00-lv_tmp /dev/dm-9 /dev/sda2 lvm xfs 4G /tmp
|-/dev/mapper/vg00-lv_home /dev/dm-10 /dev/sda2 lvm xfs 4G /home
`-/dev/mapper/vg00-lv_tanium /dev/dm-11 /dev/sda2 lvm xfs 3G /opt/Tanium
/dev/sdb /dev/sdb disk LVM2_member 350G
`-/dev/mapper/vg_util-lg_util /dev/dm-4 /dev/sdb lvm ext4 lg_util 350G /app/util
/dev/sdc /dev/sdc disk LVM2_member 540G
`-/dev/mapper/vg_rancher-lg_rancher /dev/dm-3 /dev/sdc lvm ext4 lg_rancher 540G /var/lib/rancher
What steps will reproduce the bug?¶
No response
Workaround, if any¶
Make the code better error proof - will create a PR #3631
Additional information¶
I did a debug run, but here we did not see the error.
gdha commented at 2026-09-21 12:30:¶
As PR #3631 has been merged we can close this issue.
[Export of Github issue for rear/rear.]