#3201 Issue closed: are these errors a problem?¶
Labels: support / question, no-issue-activity
hspindel opened issue at 2024-04-07 03:27:¶
- ReaR version ("/usr/sbin/rear -V"):
2.7
-
If your ReaR version is not the current version, explain why you can't upgrade:
-
OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"):
NAME="Rocky Linux"
VERSION="9.3 (Blue Onyx)"
ID="rocky"
ID_LIKE="rhel centos fedora"
VERSION_ID="9.3"
PLATFORM_ID="platform:el9"
PRETTY_NAME="Rocky Linux 9.3 (Blue Onyx)"
ANSI_COLOR="0;32"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:rocky:rocky:9::baseos"
HOME_URL="https://rockylinux.org/"
BUG_REPORT_URL="https://bugs.rockylinux.org/"
SUPPORT_END="2032-05-31"
ROCKY_SUPPORT_PRODUCT="Rocky-Linux-9"
ROCKY_SUPPORT_PRODUCT_VERSION="9.3"
REDHAT_SUPPORT_PRODUCT="Rocky Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="9.3"
- ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
OUTPUT=ISO
BACKUP=NETFS
BACKUP_URL=cifs://192.1.1.12/rocky-dd
BACKUP_OPTIONS="cred=/etc/rear/creds,vers=2.1"
USE_RAMDISK=0
BACKUP_PROG_EXCLUDE=( "${BACKUP_PROG_EXCLUDE[@]}" '/home/timeshift' )
- Hardware vendor/product (PC or PowerNV BareMetal or ARM) or VM (KVM guest or PowerVM LPAR):
Dell T7910
- 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):
BIOS. GRUB.
- Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
Local mdadm RAID 5, 4 4TB HDD
- Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,LABEL,SIZE,MOUNTPOINT"):
[root@server2 howard]# lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,LABEL,SIZE,MOUNTPOINT
NAME KNAME PKNAME TRAN TYPE FSTYPE LABEL SIZE MOUNTPOI
/dev/sda /dev/sda usb disk 0B
/dev/sdb /dev/sdb usb disk 0B
/dev/sdc /dev/sdc usb disk 0B
/dev/sdd /dev/sdd usb disk 0B
/dev/sde /dev/sde sas disk 3.6T
|-/dev/sde1 /dev/sde1 /dev/sde part 1M
|-/dev/sde2 /dev/sde2 /dev/sde part xfs 1G /boot
|-/dev/sde3 /dev/sde3 /dev/sde part LVM2_member 21.4G
| |-/dev/mapper/rl_server2-root
| | /dev/dm-0 /dev/sde3 lvm xfs 70G /
| `-/dev/mapper/rl_server2-swap
| /dev/dm-1 /dev/sde3 lvm swap 15.7G [SWAP]
`-/dev/sde4 /dev/sde4 /dev/sde part linux_raid_member server2:home 3.6T
`-/dev/md127 /dev/md127 /dev/sde4 raid5 xfs 10.8T /home
/dev/sdf /dev/sdf sas disk 3.6T
|-/dev/sdf1 /dev/sdf1 /dev/sdf part LVM2_member 21.4G
| `-/dev/mapper/rl_server2-root
| /dev/dm-0 /dev/sdf1 lvm xfs 70G /
`-/dev/sdf2 /dev/sdf2 /dev/sdf part linux_raid_member server2:home 3.6T
`-/dev/md127 /dev/md127 /dev/sdf2 raid5 xfs 10.8T /home
/dev/sdg /dev/sdg sas disk 3.6T
|-/dev/sdg1 /dev/sdg1 /dev/sdg part LVM2_member 21.4G
| `-/dev/mapper/rl_server2-root
| /dev/dm-0 /dev/sdg1 lvm xfs 70G /
`-/dev/sdg2 /dev/sdg2 /dev/sdg part linux_raid_member server2:home 3.6T
`-/dev/md127 /dev/md127 /dev/sdg2 raid5 xfs 10.8T /home
/dev/sdh /dev/sdh sas disk 3.6T
|-/dev/sdh1 /dev/sdh1 /dev/sdh part LVM2_member 21.4G
| `-/dev/mapper/rl_server2-root
| /dev/dm-0 /dev/sdh1 lvm xfs 70G /
`-/dev/sdh2 /dev/sdh2 /dev/sdh part linux_raid_member server2:home 3.6T
`-/dev/md127 /dev/md127 /dev/sdh2 raid5 xfs 10.8T /home
/dev/sr0 /dev/sr0 sata rom 1024M
[root@server2 howard]#
- Description of the issue (ideally so that others can reproduce it):
rear runs to completion. Expected backup files are created. But error messages are reported as follows:
Archived 63353 MiB in 5364 seconds [avg 12094 KiB/sec]
ERROR: Unmounting '/var/tmp/rear.h64Kn9vXbQZsRIa/outputfs' failed.
Some latest log messages since the last called script 980_umount_NETFS_dir.sh:
2024-04-06 03:36:22.294409388 Archived 63353 MiB in 5364 seconds [avg 12094 KiB/sec]
2024-04-06 03:36:22.714317169 Including backup/NETFS/GNU/Linux/600_start_selinux.sh
2024-04-06 03:36:22.759003585 Including backup/NETFS/GNU/Linux/620_force_autorelabel.sh
2024-04-06 03:36:22.785127124 Including backup/NETFS/default/970_remove_lock.sh
2024-04-06 03:36:22.853179624 Unmounting '/var/tmp/rear.h64Kn9vXbQZsRIa/outputfs'
2024-04-06 03:36:22.918956518 Forced unmount of '/var/tmp/rear.h64Kn9vXbQZsRIa/outputfs'
2024-04-06 03:36:22.929532470 Unmounting '/var/tmp/rear.h64Kn9vXbQZsRIa/outputfs' failed.
Some messages from /var/tmp/rear.h64Kn9vXbQZsRIa/tmp/rear.mkbackup.stdout_stderr since the last cal
ed script 980_umount_NETFS_dir.sh:
Including backup/NETFS/GNU/Linux/310_stop_selinux.sh
Including backup/NETFS/default/400_create_include_exclude_files.sh
Including backup/NETFS/default/500_make_backup.sh
Including backup/NETFS/GNU/Linux/600_start_selinux.sh
Including backup/NETFS/GNU/Linux/620_force_autorelabel.sh
Including backup/NETFS/default/970_remove_lock.sh
umount: /var/tmp/rear.h64Kn9vXbQZsRIa/outputfs: target is busy.
umount: /var/tmp/rear.h64Kn9vXbQZsRIa/outputfs: target is busy.
Use debug mode '-d' for some debug messages or debugscript mode '-D' for full debug messages with '
et -x' output
Aborting due to an error, check /var/log/rear/rear-server2.log for details
Exiting rear mkbackup (PID 21223) and its descendant processes ...
Running exit tasks
Directory /var/tmp/rear.h64Kn9vXbQZsRIa/outputfs still mounted - trying lazy umount
Terminated
- Workaround, if any:
rear seems to work, but I am concerned whether the error messages from umount are something to worry about
- Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):
You can drag-drop log files into this editor to create an attachment
or paste verbatim text like command output or file content
by including it between a leading and a closing line of
three backticks like this:
verbatim content
pcahyna commented at 2024-04-08 17:24:¶
Does /var/tmp/rear.h64Kn9vXbQZsRIa/outputfs remain mounted after ReaR
exits? If so, is there any process using it?
(fuser -m /var/tmp/rear.h64Kn9vXbQZsRIa/outputfs should display it.)
gdha commented at 2024-04-26 09:08:¶
@hspindel Perhaps it was a small network hiccup resulting in a stale NFS situation? It is not harmful, just annoying as you need to manual unmount the temporary ReaR mount point.
hspindel commented at 2024-04-27 01:48:¶
@hspindel Perhaps it was a small network hiccup resulting in a stale NFS situation? It is not harmful, just annoying as you need to manual unmount the temporary ReaR mount point.
Okay, thank you. Good to know it's not harmful.
github-actions commented at 2024-06-26 02:17:¶
Stale issue message
[Export of Github issue for rear/rear.]