#2809 Issue closed: ReaR recover aborting du to error failed to remove /tmp/rear.xxxx/outputfs¶
Labels: support / question, fixed / solved / done
CB500X opened issue at 2022-05-18 11:28:¶
Relax-and-Recover (ReaR) Issue Template¶
Fill in the following items before submitting a new issue
(quick response is not guaranteed with free support):
-
ReaR version ("/usr/sbin/rear -V"):
Relax-and-Recover 2.6 / 2020-06-17 -
OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"):
RHEL "fedora" 8.6 -
ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
OUTPUT=ISO
BACKUP=NETFS
BACKUP_URL=file:///mnt/backup
OUTPUT_URL=file:///mnt/backup
BACKUP_PROG_EXCLUDE=( ${BACKUP_PROG_EXCLUDE[@]} '/mnt/*' )
-
Hardware vendor/product (PC or PowerNV BareMetal or ARM) or VM (KVM guest or PowerVM LPAR):
Vmware 6.7 -
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):
VM local storage -
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 30G
|-/dev/sda1 /dev/sda1 /dev/sda part xfs 1G /boot
`-/dev/sda2 /dev/sda2 /dev/sda part LVM2_membe 29G
|-/dev/mapper/rhel_mop4px01ext-root /dev/dm-0 /dev/sda2 lvm xfs 16G /
|-/dev/mapper/rhel_mop4px01ext-swap /dev/dm-1 /dev/sda2 lvm swap 2.1G [SWAP]
|-/dev/mapper/rhel_mop4px01ext-tmp /dev/dm-2 /dev/sda2 lvm xfs 10.8G /tmp
|-/dev/mapper/rhel_mop4px01ext-var_log_audit /dev/dm-3 /dev/sda2 lvm xfs 1G /var/log/audit
|-/dev/mapper/rhel_mop4px01ext-var /dev/dm-4 /dev/sda2 lvm xfs 3G /var
|-/dev/mapper/rhel_mop4px01ext-home /dev/dm-5 /dev/sda2 lvm xfs 1G /home
|-/dev/mapper/rhel_mop4px01ext-var_log /dev/dm-6 /dev/sda2 lvm xfs 2G /var/log
`-/dev/mapper/rhel_mop4px01ext-var_tmp /dev/dm-7 /dev/sda2 lvm xfs 3G /var/tmp
/dev/sdb /dev/sdb disk ext2 backup 15G /mnt/backup
/dev/sdc /dev/sdc disk 10G
`-/dev/sdc1 /dev/sdc1 /dev/sdc part LVM2_membe 10G
`-/dev/mapper/rhel_mop4px01ext-tmp /dev/dm-2 /dev/sdc1 lvm xfs 10.8G /tmp
/dev/sr0 /dev/sr0 sata rom 1024M
- Description of the issue (ideally so that others can reproduce it):
Boot on rescue ISO, create /mnt/backup folder as source, scp backup.tar.gz to target, then launch 'rear rescue' anything is running well but at this end I get the following message :
BUG in /usr/share/rear/lib/framework-functions.sh line 138
'Directory /tmp/rear.dVbvg4JGj7ESDJH/outputfs not empty, can not remove'
-
Workaround, if any:
None -
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
Some latest log messages since the last called script 990_copy_logfile.sh:
'-rear,25232 /bin/rear recover
'-pstree,25233 -Aplau 832
/usr/share/rear/lib/_input-output-functions.sh: line 151: kill: (252367) - No such process
2022-05-18 11:91:28.936385576 Running exit tasks
2022-05-18 11:91:28.955038237 Finished in 98 seconds
2022-05-18 11:91:28.956730929 Removing build area /tmp/rear.dVbvg4JGj7ESDJH
rmdir: removing directory, '/tmp/rear.dVbvg4JGj7ESDJH/outputfs'
rmdir: failed to remove '/tmp/rear.dVbvg4JGj7ESDJH/outputfs': Directory not empty
Aborting due to an error, check /var/log/rear/rear-MOP4PX01EXT.log for details
Terminated
RESCUE MOP4PX01EXT:~ # rear version
ERROR: The workflow version is not supported in the ReaR rescue/recouery system
Some latest log messages since the last called script 050_check_rear_recovermode.sh:
2022-05-18 11:56:11.759010928 Including init/default./050_check_rear_recovermode.sh
Aborting due to an error, check /var/log/rear/rear-MOP4PX01EXT.log for details
Terminated
pcahyna commented at 2022-05-18 12:48:¶
rmdir: failed to remove '/tmp/rear.dVbvg4JGj7ESDJH/outputfs': Directory not empty
Can you please look what is under /tmp/rear.dVbvg4JGj7ESDJH/outputfs ?
Is anything mounted there?
BACKUP_URL=file:///mnt/backup OUTPUT_URL=file:///mnt/backupcreate /mnt/backup folder as source, scp backup.tar.gz to target, then launch 'rear rescue'
I must admit, I have never tested any similar procedure.
CB500X commented at 2022-05-20 15:13:¶
Hello pcahyna,
Thanks for this answer.
In fact there is a mismatch in my description.
This is a job I use to do on RHEL 7.x.
First I backup my server locally in the /mnt/backup directory
BACKUP=NETFS
BACKUP_URL=file:///mnt/backup/
When recovering, I create a VM same as original.
Then I boot this VM with the ISO I get from the backed up computer
Once booted with ReaR, I recreate the /mnt/backup directory and I copy
the backup.tar.gz from the backed up computer.
Then I launch rear recover (not rear rescue as I said in the first
post).
Anything is running well but when rebooting computer it is starting in
recovery mode as it is not able to remount the /mnt/backup folder (in
the fstab : LABEL=backup /mnt/backup ext2 defaults 0 0).
Let me know if you need more info.
Cordialement, Regards.
Etienne Pottier
IT Specialist
Global Market
+33-1-4941-7872
Tie-Line: 38-757872
***@***.***
11 Avenue du Mont d'Est, 93881, Noisy-le-grand, France
[cid:7ec0570f-cc87-4d7c-9ac7-39bbbe3d5600]
From: pcahyna ***@***.***>
Sent: Wednesday, May 18, 2022 2:48 PM
To: rear/rear ***@***.***>
Cc: Etienne Pottier ***@***.***>; Author
***@***.***>
Subject: [EXTERNAL] Re: [rear/rear] ReaR recover aborting du to
error failed to remove /tmp/rear.xxxx/outputfs (Issue #2809)
rmdir: failed to remove '/tmp/rear.dVbvg4JGj7ESDJH/outputfs': Directory
not empty Can you please look what is under
/tmp/rear.dVbvg4JGj7ESDJH/outputfs ? Is anything mounted there?
BACKUP_URL=file:///mnt/backup OUTPUT_URL=file:///mnt/backup
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
rmdir: failed to remove '/tmp/rear.dVbvg4JGj7ESDJH/outputfs': Directory not empty
Can you please look what is under /tmp/rear.dVbvg4JGj7ESDJH/outputfs ? Is anything mounted there?
BACKUP_URL=file:///mnt/backup
OUTPUT_URL=file:///mnt/backup
create /mnt/backup folder as source, scp backup.tar.gz to target, then launch 'rear rescue'
I must admit, I have never tested any similar procedure.
—
Reply to this email directly, view it on
GitHubhttps://github.com/rear/rear/issues/2809#issuecomment-1129964181,
or
unsubscribehttps://github.com/notifications/unsubscribe-auth/AZHCHKAJQXOVJPTAHD4XNR3VKTRLLANCNFSM5WIEKWWQ.
You are receiving this because you authored the thread.Message ID:
***@***.***>
Unless otherwise stated above:
Compagnie IBM France
Siège Social : 17, avenue de l'Europe, 92275 Bois-Colombes Cedex
RCS Nanterre 552 118 465
Forme Sociale : S.A.S.
Capital Social : 663.779.730,90 €
SIRET : 552 118 465 03644 - Code NAF 6203Z
github-actions commented at 2022-07-20 03:26:¶
Stale issue message
pcahyna commented at 2022-07-25 09:09:¶
Hello Etienne,
Anything is running well but when rebooting computer it is starting in recovery mode as it is not able to remount the /mnt/backup folder (in the fstab : LABEL=backup /mnt/backup ext2 defaults 0 0).
So, the BUG "Directory /tmp/rear.dVbvg4JGj7ESDJH/outputfs not empty, can not remove" is not a problem anymore?
CB500X commented at 2022-07-25 09:49:¶
Hello,
No, this is not a pb anymore, you can close the request.
Thanks for that.
Cordialement, Regards.
Etienne Pottier
IT Specialist
Global Market
+33-1-4941-7872
Tie-Line: 38-757872
***@***.***
11 Avenue du Mont d'Est, 93881, Noisy-le-grand, France
[cid:933bac98-93ef-44b8-85e1-bed4ed4db6e7]
From: pcahyna ***@***.***>
Sent: Monday, July 25, 2022 11:09 AM
To: rear/rear ***@***.***>
Cc: Etienne Pottier ***@***.***>; Author
***@***.***>
Subject: [EXTERNAL] Re: [rear/rear] ReaR recover aborting du to
error failed to remove /tmp/rear.xxxx/outputfs (Issue #2809)
Hello Etienne, Anything is running well but when rebooting computer it
is starting in recovery mode as it is not able to remount the
/mnt/backup folder (in the fstab : LABEL=backup /mnt/backup ext2
defaults 0 0). So, the BUG "Directory
/tmp/rear.dVbvg4JGj7ESDJH/outputfs
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
Hello Etienne,
Anything is running well but when rebooting computer it is starting in recovery mode as it is not able to remount the /mnt/backup folder (in the fstab : LABEL=backup /mnt/backup ext2 defaults 0 0).
So, the BUG "Directory /tmp/rear.dVbvg4JGj7ESDJH/outputfs not empty, can not remove" is not a problem anymore?
—
Reply to this email directly, view it on
GitHubhttps://github.com/rear/rear/issues/2809#issuecomment-1193786350,
or
unsubscribehttps://github.com/notifications/unsubscribe-auth/AZHCHKCFUX5X5PVK67SFNETVVZKUBANCNFSM5WIEKWWQ.
You are receiving this because you authored the thread.Message ID:
***@***.***>
Unless otherwise stated above:
Compagnie IBM France
Siège Social : 17, avenue de l'Europe, 92275 Bois-Colombes Cedex
RCS Nanterre 552 118 465
Forme Sociale : S.A.S.
Capital Social : 663.779.730,90 €
SIRET : 552 118 465 03644 - Code NAF 6203Z
pcahyna commented at 2022-07-25 09:51:¶
Thanks for the information, for the record, do you please know what the problem was, and how did you solve it?
CB500X commented at 2022-07-25 10:06:¶
Hello,
In fact I do not know what the problem was really with the temp
folder.
I did another backup, and the second time the issue disappear, so I did
not investigate more on this.
Thanks
Cordialement, Regards.
Etienne Pottier
IT Specialist
Global Market
+33-1-4941-7872
Tie-Line: 38-757872
***@***.***
11 Avenue du Mont d'Est, 93881, Noisy-le-grand, France
[cid:4c8184af-97de-4db9-b847-8f9224380b2b]
From: pcahyna ***@***.***>
Sent: Monday, July 25, 2022 11:52 AM
To: rear/rear ***@***.***>
Cc: Etienne Pottier ***@***.***>; Author
***@***.***>
Subject: [EXTERNAL] Re: [rear/rear] ReaR recover aborting du to
error failed to remove /tmp/rear.xxxx/outputfs (Issue #2809)
Thanks for the information, for the record, do you please know what the
problem was, and how did you solve it? — Reply to this email directly,
view it on GitHub, or unsubscribe. You are receiving this because you
authored the thread.
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
Thanks for the information, for the record, do you please know what the problem was, and how did you solve it?
—
Reply to this email directly, view it on
GitHubhttps://github.com/rear/rear/issues/2809#issuecomment-1193830553,
or
unsubscribehttps://github.com/notifications/unsubscribe-auth/AZHCHKEIXOC6EKURGQABDNLVVZPUBANCNFSM5WIEKWWQ.
You are receiving this because you authored the thread.Message ID:
***@***.***>
Unless otherwise stated above:
Compagnie IBM France
Siège Social : 17, avenue de l'Europe, 92275 Bois-Colombes Cedex
RCS Nanterre 552 118 465
Forme Sociale : S.A.S.
Capital Social : 663.779.730,90 €
SIRET : 552 118 465 03644 - Code NAF 6203Z
[Export of Github issue for rear/rear.]