-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remote webdav cloud storage not applicable for TMPDIR on low HD space? #2983
Comments
and also
in etc/rear/local.conf do not work because usr/sbin/rear How to set TMPDIR properly see the description in
For me it works as described:
But I do not have a "remote webdav-Drive from IONOS" The error messages you get like
do not make sense because the script '005_verify_os_conf.sh' The code that does this is in usr/share/rear/lib/framework-functions.sh For me this code works in ReaR and also on command line
Usually such inexplicable error messages indicate You may try out the current ReaR upstream GitHub master code |
@johannes
In general, the workaround to set the TMPDIR outside the rear
configuration seems to work.
I also tried to use the most updated code from GITHIB for rear with the
following results:
- Without changing the TMPDIR to the mounted partiton, the system begins
to run (and later on runs out of disk space as expected)
- With the TMPDIR pointing to the mounted partition, all kinds of errors
occur and the system aborts
I do suspect that the webdav mounting is not compatible with the rear
software - if any remote mounted at all.
I guess I need to change at least the protocoll to SSHFS but this is no
current option of the mounted partition.
Thanks at this time for your really professional answer.
Best
Andreas
Am 11.05.2023 um 12:32 schrieb Johannes Meixner:
… @andreasberner <https://github.com/andreasberner>
|TMPDIR=/mnt/hidrive/tmp |
and also
|export TMPDIR=/mnt/hidrive/tmp |
in etc/rear/local.conf do not work because usr/sbin/rear
creates its temporary working area (BUILD_DIR) at
https://github.com/rear/rear/blob/master/usr/sbin/rear#L505
before the config files get sourced later at
https://github.com/rear/rear/blob/master/usr/sbin/rear#L598
How to set TMPDIR properly see the description in
usr/share/rear/conf/default.conf
(excerpts)
|# TMPDIR # # Relax-and-Recover needs a (temporary) working area where
it builds in particular # the rescue/recovery system ISO image (and
perhaps even stores the backup archive). ... # To have a specific
working area directory prefix for Relax-and-Recover call # export
TMPDIR="/prefix/for/rear/working/directory" # before calling 'rear'
(/prefix/for/rear/working/directory must already exist). |
For me it works as described:
|# mount -v /dev/sda6 /other # mkdir /other/tmp # export
TMPDIR=/other/tmp # usr/sbin/rear -D mkrescue Relax-and-Recover 2.7 /
Git Running rear mkrescue (PID 26919 date 2023-05-11 12:19:23) Command
line options: usr/sbin/rear -D mkrescue Using log file:
/root/rear.github.master/var/log/rear/rear-linux-h9wr.log Using build
area: /other/tmp/rear.TxZuJW4iSV3Cwpd ... |
But I do not have a "remote webdav-Drive from IONOS"
to test how ReaR behaves with that.
The error messages you get like
|Script 'default/005_verify_os_conf.sh' without leading 3-digit number
'NNN_' ... |
do not make sense because the script '005_verify_os_conf.sh'
has a leading 3-digit number 'NNN_'.
The code that does this is in usr/share/rear/lib/framework-functions.sh
https://github.com/rear/rear/blob/master/usr/share/rear/lib/framework-functions.sh#L128
For me this code works in ReaR and also on command line
|# script='default/005_verify_os_conf.sh' # grep -q
'^[0-9][0-9][0-9]_' <<< $( basename $script ) || echo "Script
'$script' without leading 3-digit number 'NNN_'" [no output] #
script='default/05_verify_os_conf.sh' # grep -q '^[0-9][0-9][0-9]_'
<<< $( basename $script ) || echo "Script '$script' without leading
3-digit number 'NNN_'" Script 'default/05_verify_os_conf.sh' without
leading 3-digit number 'NNN_' #
script='default/0500_verify_os_conf.sh' # grep -q '^[0-9][0-9][0-9]_'
<<< $( basename $script ) || echo "Script '$script' without leading
3-digit number 'NNN_'" Script 'default/0500_verify_os_conf.sh' without
leading 3-digit number 'NNN_' |
Usually such inexplicable error messages indicate
that the ReaR installation might be somehow messed up
or that the environment where ReaR is run
is not sufficiently standards compliant.
You may try out the current ReaR upstream GitHub master code
from within a separated directory as a test to find out
if things work better then, see the section
"Testing current ReaR upstream GitHub master code" in
https://en.opensuse.org/SDB:Disaster_Recovery
—
Reply to this email directly, view it on GitHub
<#2983 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEA7Q5WFSXKWZPNN4POZNQLXFS53ZANCNFSM6AAAAAAX3AKDUA>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@andreasberner The ReaR software is only bash scripts (and documentation) So when things work without errors (up to "out of space") So - as far as I understand it - it is the "webdav TMPDIR" Perhaps you can change something how that "remote webdav-Drive" A different idea: What exactly did run out of space with the default TMPDIR? Relly out of disk space (i.e. physical or virtual harddisk)? Or is it perhaps actually out of memory (RAM plus swap)? Check the output of 'df' and 'free' what actually runs out of space. Because ReaR 2.7 uses by default /var/tmp for its When you run ReaR in debug modes (via -d or -D) |
Hi Johannes,
thanks for your response. There seems to be still a problem in using
remote filesystems for the TMPDIR.
While the webdav protocoll sucks with the below given error messages, a
sshfs-mounted TMPDIR fails with other error messages like described in
https://debianforum.de/forum/viewtopic.php?t=182913#:~:text=ALLES%20AUSW%C3%84HLEN-,Creating%20recovery%20system%20root%20filesystem%20skeleton%20layout%0AERROR%3A%20Failed%20to%20copy,an%20error%2C%20check%20/var/log/rear/rear%2Ddebian.log%20for%20details,-Das%20o.g
When you mention your working example in your reply, can you please
specify details about the mounted filesystem /other?
Especially, is it a local filesystem or a remote filesystem? If remote,
which protocoll is used for the mounting? NFS, SSHFS ?
Thanks in advance and best regards
Andreas
Am 11.05.2023 um 12:32 schrieb Johannes Meixner:
… @andreasberner <https://github.com/andreasberner>
|TMPDIR=/mnt/hidrive/tmp |
and also
|export TMPDIR=/mnt/hidrive/tmp |
in etc/rear/local.conf do not work because usr/sbin/rear
creates its temporary working area (BUILD_DIR) at
https://github.com/rear/rear/blob/master/usr/sbin/rear#L505
before the config files get sourced later at
https://github.com/rear/rear/blob/master/usr/sbin/rear#L598
How to set TMPDIR properly see the description in
usr/share/rear/conf/default.conf
(excerpts)
|# TMPDIR # # Relax-and-Recover needs a (temporary) working area where
it builds in particular # the rescue/recovery system ISO image (and
perhaps even stores the backup archive). ... # To have a specific
working area directory prefix for Relax-and-Recover call # export
TMPDIR="/prefix/for/rear/working/directory" # before calling 'rear'
(/prefix/for/rear/working/directory must already exist). |
For me it works as described:
|# mount -v /dev/sda6 /other # mkdir /other/tmp # export
TMPDIR=/other/tmp # usr/sbin/rear -D mkrescue Relax-and-Recover 2.7 /
Git Running rear mkrescue (PID 26919 date 2023-05-11 12:19:23) Command
line options: usr/sbin/rear -D mkrescue Using log file:
/root/rear.github.master/var/log/rear/rear-linux-h9wr.log Using build
area: /other/tmp/rear.TxZuJW4iSV3Cwpd ... |
But I do not have a "remote webdav-Drive from IONOS"
to test how ReaR behaves with that.
The error messages you get like
|Script 'default/005_verify_os_conf.sh' without leading 3-digit number
'NNN_' ... |
do not make sense because the script '005_verify_os_conf.sh'
has a leading 3-digit number 'NNN_'.
The code that does this is in usr/share/rear/lib/framework-functions.sh
https://github.com/rear/rear/blob/master/usr/share/rear/lib/framework-functions.sh#L128
For me this code works in ReaR and also on command line
|# script='default/005_verify_os_conf.sh' # grep -q
'^[0-9][0-9][0-9]_' <<< $( basename $script ) || echo "Script
'$script' without leading 3-digit number 'NNN_'" [no output] #
script='default/05_verify_os_conf.sh' # grep -q '^[0-9][0-9][0-9]_'
<<< $( basename $script ) || echo "Script '$script' without leading
3-digit number 'NNN_'" Script 'default/05_verify_os_conf.sh' without
leading 3-digit number 'NNN_' #
script='default/0500_verify_os_conf.sh' # grep -q '^[0-9][0-9][0-9]_'
<<< $( basename $script ) || echo "Script '$script' without leading
3-digit number 'NNN_'" Script 'default/0500_verify_os_conf.sh' without
leading 3-digit number 'NNN_' |
Usually such inexplicable error messages indicate
that the ReaR installation might be somehow messed up
or that the environment where ReaR is run
is not sufficiently standards compliant.
You may try out the current ReaR upstream GitHub master code
from within a separated directory as a test to find out
if things work better then, see the section
"Testing current ReaR upstream GitHub master code" in
https://en.opensuse.org/SDB:Disaster_Recovery
—
Reply to this email directly, view it on GitHub
<#2983 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEA7Q5WFSXKWZPNN4POZNQLXFS53ZANCNFSM6AAAAAAX3AKDUA>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
what is mounted at /other is
I never tried a remote filesystem for TMPDIR. |
I see. My problem is that the server to be backed up is a hosted server and the internal HDD is almost full or at least not sufficient remaining capacity to back up the system before copying the result to an other server. That is why I am looking for an alternate solution to back up directly on a remote HDD. Any idea how to achieve that? |
@andreasberner For my tests with ReaR I use almost always
which results on 'NFS.server.IP.address' |
Stale issue message |
ReaR version ("/usr/sbin/rear -V"):
2.7
OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"):
Debian 11.13
ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
Hardware vendor/product (PC or PowerNV BareMetal or ARM) or VM (KVM guest or PowerVM LPAR):
VM from netcup, germany
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):
I guess BIOS
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
local HD and remote webdav-Drive from IONOS, Germany, supposed for TMPFILE and
Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,LABEL,SIZE,MOUNTPOINT"):
I would like to make an ISO file with a complete backup over the net to a remote clould storage.
The cloud is accessable via webdav protocoll.
During the backup process the internal HD runs out of space because the iso file is created locally and subsequently copied to the backup target.
I tried to overcome this shortage by changing the TMPDIR to the webdav drive by using
TMPDIR=/mnt/hidrive/tmp
but
# rear -v mkbackup
leads to errors like
and then the backup aborts.
What can I do to solve this problem of low local HD-space?
The text was updated successfully, but these errors were encountered: