#2584 Issue closed: "rear recover" fails on sles15sp1 and sles15sp2 with btrfs on POWER P9 9009-42A--LPAR¶
Labels: support / question, special hardware or VM,
no-issue-activity
mantriharish opened issue at 2021-03-08 07:52:¶
ISSUE
WE HAVE UPGRADED OUR SYSTEM FROM SLES12SP5 TO SLES15SP1
AFTER WHICH WE TOOK THE REAR BACKUP OF THE SERVER AND
TRIED TO RESTORE IT ON ANOTHER SERVER TO SEE IF THE SERVER
COMES UP FINE OR NOT,,BUT WE ARE GETTING THE BELOW ERROR
ERROR
Creating filesystem of type btrfs with mount point / on /dev/mapper/rootvg-rootvol.
Mounting filesystem /
/usr/lib/snapper/installation-helper not executable may indicate an error with btrfs default subvolume setup for @/.snapshots/1/snapshot on /dev/mapper/rootvg-rootvol
NOTE:WE GET THE ABOVE ERROR NOT ONLY WHEN THE SERVER
REAR BACKUP IS TAKEN WHEN THE SERVER RUN ON SLES15SP1
IT THE SAME CASE ON SLES15SP2 AS WELL ,,I WOULD ALSO BRING
TO YOUR NOTICE THAT I HAVE USED 2 VERSION OF REAR BACKUP
AS BELOW BUT THE ERROR REMAINS THE SAME
rear23a-2.3.a-9.6.1.ppc64le
THIS IS DIRECTLY FROM YOUR REPOSITORY SITE
rear-2.6-142.git.4265.4b43f43.master.ppc64le.rpm
THIS IS DOWNLOADED FROM THE REAR RECOVER SITE
BUT THIS WORKS ONLY ON SLES15SP2
IT DOES NOT WORK ON SLES15SP1 BECAUSE OF RPM DEPENDENCIES
CURRENT SET OF INFORMATION I AM GIVING
IS FROM SLES15SP1 REAR BACKUP DETAILS
- ReaR version
("/usr/sbin/rear -V")
hedcb019:~ # /usr/sbin/rear -V
Relax-and-Recover 2.4 / Git
- Operating system version
("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf")
hedcb019:~ # cat /etc/os-release
NAME="SLES"
VERSION="15-SP1"
VERSION_ID="15.1"
PRETTY_NAME="SUSE Linux Enterprise Server 15 SP1"
ID="sles"
ID_LIKE="suse"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles:15:sp1"
- ReaR configuration files
("cat /etc/rear/local.conf" and/or "cat /etc/rear/site.conf")
hedcb019:~ # cat /etc/rear/local.conf
# Default is to create Relax-and-Recover rescue media as ISO image
# set OUTPUT to change that
# set BACKUP to activate an automated (backup and) restore of your data
# Possible configuration values can be found in /usr/share/rear/conf/default.conf
#
# This file (local.conf) is intended for manual configuration. For configuration
# through packages and other automated means we recommend creating a new
# file named site.conf next to this file and to leave the local.conf as it is.
# Our packages will never ship with a site.conf.
hedcb019:~ # cat /etc/rear/site.conf
OUTPUT=ISO
ISO_PREFIX=ROOTVGonly-rear-$HOSTNAME
BACKUP=NETFS
BACKUP_URL=nfs://10.254.11.236/suse_backups
BACKUP_OPTIONS=nfsvers=3,nolock
ONLY_INCLUDE_VG=( "rootvg" )
BACKUP_PROG_EXCLUDE=( '/tmp/*' '/dev/shm/*' '/home/rear/*' '/mnt/*' )
SSH_ROOT_PASSWORD="test4backup"
BOOT_OVER_SAN=Y
AUTOEXCLUDE_MULTIPATH=n
- Hardware (PC or PowerNV BareMetal or ARM)
or virtual machine (KVM guest or PoverVM LPAR)
POWER P9 9009-42A--LPAR
- System architecture
(x86 compatible or PPC64/PPC64LE or what exact ARM device)
PPC64LE
- Firmware (BIOS or UEFI or Open Firmware)
and bootloader (GRUB or ELILO or Petitboot)
attaching supportconfig of the server
- Storage (local disk or SSD)
and/or SAN (FC or iSCSI or FCoE)
and/or multipath (DM or NVMe)
SAN ---FCS----MULTIPAHT
- The output of
lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,SIZE,MOUNTPOINT
hedcb019:/boot/grub2 # lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,SIZE,MOUNTPOINT
NAME KNAME PKNAME TRAN TYPE FSTYPE SIZE MOUNTPOINT
/dev/sda /dev/sda disk mpath_member 50G
|-/dev/sda1 /dev/sda1 /dev/sda part mpath_member 6.8M
|-/dev/sda2 /dev/sda2 /dev/sda part LVM2_member 50G
`-/dev/mapper/mpatha /dev/dm-0 /dev/sda mpath 50G
|-/dev/mapper/mpatha-part1 /dev/dm-1 /dev/dm-0 part 6.8M
`-/dev/mapper/mpatha-part2 /dev/dm-2 /dev/dm-0 part LVM2_member 50G
|-/dev/mapper/rootvg-rootvol /dev/dm-3 /dev/dm-2 lvm btrfs 29.8G /
|-/dev/mapper/rootvg-swapvol /dev/dm-4 /dev/dm-2 lvm swap 2G [SWAP]
|-/dev/mapper/rootvg-expvol /dev/dm-5 /dev/dm-2 lvm btrfs 992M /exploit
|-/dev/mapper/rootvg-homevol /dev/dm-6 /dev/dm-2 lvm btrfs 992M /home
|-/dev/mapper/rootvg-iemvol /dev/dm-7 /dev/dm-2 lvm btrfs 3G /var/opt/BESClient
|-/dev/mapper/rootvg-optvol /dev/dm-8 /dev/dm-2 lvm btrfs 2G /opt
`-/dev/mapper/rootvg-varlogvol /dev/dm-9 /dev/dm-2 lvm btrfs 2G /var/log
/dev/sdb /dev/sdb disk mpath_member 50G
|-/dev/sdb1 /dev/sdb1 /dev/sdb part mpath_member 6.8M
|-/dev/sdb2 /dev/sdb2 /dev/sdb part LVM2_member 50G
`-/dev/mapper/mpatha /dev/dm-0 /dev/sdb mpath 50G
|-/dev/mapper/mpatha-part1 /dev/dm-1 /dev/dm-0 part 6.8M
`-/dev/mapper/mpatha-part2 /dev/dm-2 /dev/dm-0 part LVM2_member 50G
|-/dev/mapper/rootvg-rootvol /dev/dm-3 /dev/dm-2 lvm btrfs 29.8G /
|-/dev/mapper/rootvg-swapvol /dev/dm-4 /dev/dm-2 lvm swap 2G [SWAP]
|-/dev/mapper/rootvg-expvol /dev/dm-5 /dev/dm-2 lvm btrfs 992M /exploit
|-/dev/mapper/rootvg-homevol /dev/dm-6 /dev/dm-2 lvm btrfs 992M /home
|-/dev/mapper/rootvg-iemvol /dev/dm-7 /dev/dm-2 lvm btrfs 3G /var/opt/BESClient
|-/dev/mapper/rootvg-optvol /dev/dm-8 /dev/dm-2 lvm btrfs 2G /opt
`-/dev/mapper/rootvg-varlogvol /dev/dm-9 /dev/dm-2 lvm btrfs 2G /var/log
/dev/sdc /dev/sdc disk mpath_member 50G
|-/dev/sdc1 /dev/sdc1 /dev/sdc part mpath_member 6.8M
|-/dev/sdc2 /dev/sdc2 /dev/sdc part LVM2_member 50G
`-/dev/mapper/mpatha /dev/dm-0 /dev/sdc mpath 50G
|-/dev/mapper/mpatha-part1 /dev/dm-1 /dev/dm-0 part 6.8M
`-/dev/mapper/mpatha-part2 /dev/dm-2 /dev/dm-0 part LVM2_member 50G
|-/dev/mapper/rootvg-rootvol /dev/dm-3 /dev/dm-2 lvm btrfs 29.8G /
|-/dev/mapper/rootvg-swapvol /dev/dm-4 /dev/dm-2 lvm swap 2G [SWAP]
|-/dev/mapper/rootvg-expvol /dev/dm-5 /dev/dm-2 lvm btrfs 992M /exploit
|-/dev/mapper/rootvg-homevol /dev/dm-6 /dev/dm-2 lvm btrfs 992M /home
|-/dev/mapper/rootvg-iemvol /dev/dm-7 /dev/dm-2 lvm btrfs 3G /var/opt/BESClient
|-/dev/mapper/rootvg-optvol /dev/dm-8 /dev/dm-2 lvm btrfs 2G /opt
`-/dev/mapper/rootvg-varlogvol /dev/dm-9 /dev/dm-2 lvm btrfs 2G /var/log
/dev/sdd /dev/sdd disk mpath_member 50G
|-/dev/sdd1 /dev/sdd1 /dev/sdd part mpath_member 6.8M
|-/dev/sdd2 /dev/sdd2 /dev/sdd part LVM2_member 50G
`-/dev/mapper/mpatha /dev/dm-0 /dev/sdd mpath 50G
|-/dev/mapper/mpatha-part1 /dev/dm-1 /dev/dm-0 part 6.8M
`-/dev/mapper/mpatha-part2 /dev/dm-2 /dev/dm-0 part LVM2_member 50G
|-/dev/mapper/rootvg-rootvol /dev/dm-3 /dev/dm-2 lvm btrfs 29.8G /
|-/dev/mapper/rootvg-swapvol /dev/dm-4 /dev/dm-2 lvm swap 2G [SWAP]
|-/dev/mapper/rootvg-expvol /dev/dm-5 /dev/dm-2 lvm btrfs 992M /exploit
|-/dev/mapper/rootvg-homevol /dev/dm-6 /dev/dm-2 lvm btrfs 992M /home
|-/dev/mapper/rootvg-iemvol /dev/dm-7 /dev/dm-2 lvm btrfs 3G /var/opt/BESClient
|-/dev/mapper/rootvg-optvol /dev/dm-8 /dev/dm-2 lvm btrfs 2G /opt
`-/dev/mapper/rootvg-varlogvol /dev/dm-9 /dev/dm-2 lvm btrfs 2G /var/log
/dev/sr0 /dev/sr0 rom iso9660 648.3M
/dev/sr1 /dev/sr1 rom iso9660 5.2G
- Debug log file of "rear -d -D mkbackup" or "rear -d -D mkrescue"
that matches the "rear recover" failure
(i.e. debug log of what created the ReaR recovery system where "rear recover" failed)
RESCUE hedcb019:~ # rear -d -D mkbackup
Relax-and-Recover 2.4 / Git
Running rear mkbackup (PID 10333)
Using log file: /var/log/rear/rear-hedcb019.log
ERROR: The workflow mkbackup is not supported in the ReaR rescue/recovery system
Some latest log messages since the last called script 050_check_rear_recover_mode.sh:
2021-03-08 07:25:53.158094234 Including init/default/050_check_rear_recover_mode.sh
2021-03-08 07:25:53.159184564 Entering debugscripts mode via 'set -x'.
Aborting due to an error, check /var/log/rear/rear-hedcb019.log for details
Exiting rear mkbackup (PID 10333) and its descendant processes
Running exit tasks
Terminated
RESCUE hedcb019:~ # rear -d -D mkrescue
Relax-and-Recover 2.4 / Git
Running rear mkrescue (PID 10612)
Using log file: /var/log/rear/rear-hedcb019.log
ERROR: The workflow mkrescue is not supported in the ReaR rescue/recovery system
Some latest log messages since the last called script 050_check_rear_recover_mode.sh:
2021-03-08 07:26:21.650984286 Including init/default/050_check_rear_recover_mode.sh
2021-03-08 07:26:21.652069429 Entering debugscripts mode via 'set -x'.
Aborting due to an error, check /var/log/rear/rear-hedcb019.log for details
Exiting rear mkrescue (PID 10612) and its descendant processes
Running exit tasks
Terminated
- Debug log file of "rear -d -D recover"
from the ReaR recovery system where "rear recover" failed
I have made the attachement
- Contents of the /var/lib/rear/ directory and in its
sub-directories
from the ReaR recovery system where "rear recover" failed
I have made the attachement
mantriharish commented at 2021-03-08 07:53:¶
i am also attaching the logs requested
Uploading sles15sp1_outputs…
mantriharish commented at 2021-03-08 08:08:¶
sles15sp1_outputs.txt
sles15sp1_rearrecover.txt
- Debug log file of "rear -d -D recover"
from the ReaR recovery system where "rear recover" failed
I have made the attachement
- Contents of the /var/lib/rear/ directory and in its
sub-directories
from the ReaR recovery system where "rear recover" failed
I have made the attachement
mantriharish commented at 2021-03-08 08:10:¶
- Debug log file of "rear -d -D recover"
from the ReaR recovery system where "rear recover" failed
I have made the attachement
- Contents of the /var/lib/rear/ directory and in its
sub-directories
from the ReaR recovery system where "rear recover" failed
mantriharish commented at 2021-03-08 08:16:¶
please
mantriharish commented at 2021-03-08 08:17:¶
can you please give me your inputs on the same and do let me know if you need any additonal logs
jsmeix commented at 2021-03-09 12:24:¶
@mantriharish
your disklayout.conf contains in particular
btrfsdefaultsubvol /dev/mapper/rootvg-rootvol / 259 @/.snapshots/1/snapshot
which is the reason why there is during "rear recover" the messsage
Doing SLES12-SP1 (and later) btrfs subvolumes setup because the default subvolume path contains '@/.snapshots/'
and therefore /usr/lib/snapper/installation-helper is called to
actually do that.
To have /usr/lib/snapper/installation-helper in the ReaR recovery
system
you need in your ReaR config file
COPY_AS_IS+=( /usr/lib/snapper/installation-helper /etc/snapper/config-templates/default )
see what I wrote at
https://github.com/gdha/rear-automated-testing/issues/84#issuecomment-791436611
I still need the debug log file of "rear -d -D mkbackup" or "rear -d -D
mkrescue"
and the debug log file of "rear -d -D recover".
Additionally - because you use btrfs - I need the output of
findmnt -a -o SOURCE,TARGET,FSTYPE -t btrfs,ext2,ext3,ext4,xfs,reiserfs,vfat
I enhanced the list
"To analyze and debug a "rear recover" failure the following information
is mandatory" in
https://en.opensuse.org/SDB:Disaster_Recovery
accordingly.
jsmeix commented at 2021-03-09 12:35:¶
@mantriharish
I have the vague feeling that your brtfs setup is somewhat special.
For example on my SLES15 test system
(a KVM/QEMU virtual machine - of course no multipath)
with SUSE's default btrfs + LVM (+ LUKS in my case) I have
# lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,SIZE,MOUNTPOINT
NAME KNAME PKNAME TRAN TYPE FSTYPE SIZE MOUNTPOINT
/dev/sda /dev/sda ata disk 20G
|-/dev/sda1 /dev/sda1 /dev/sda part 8M
`-/dev/sda2 /dev/sda2 /dev/sda part crypto_LUKS 20G
`-/dev/mapper/cr_ata-QEMU_HARDDISK_QM00001-part2 /dev/dm-0 /dev/sda2 crypt LVM2_member 20G
|-/dev/mapper/system-swap /dev/dm-1 /dev/dm-0 lvm swap 2G [SWAP]
|-/dev/mapper/system-root /dev/dm-2 /dev/dm-0 lvm btrfs 12.6G /
`-/dev/mapper/system-home /dev/dm-3 /dev/dm-0 lvm xfs 5.4G /home
# findmnt -a -o SOURCE,TARGET,FSTYPE -t btrfs,ext2,ext3,ext4,xfs,reiserfs,vfat
SOURCE TARGET FSTYPE
/dev/mapper/system-root[/@/.snapshots/1/snapshot] / btrfs
/dev/mapper/system-root[/@/.snapshots] |-/.snapshots btrfs
/dev/mapper/system-root[/@/tmp] |-/tmp btrfs
/dev/mapper/system-root[/@/srv] |-/srv btrfs
/dev/mapper/system-root[/@/usr/local] |-/usr/local btrfs
/dev/mapper/system-root[/@/boot/grub2/i386-pc] |-/boot/grub2/i386-pc btrfs
/dev/mapper/system-root[/@/var] |-/var btrfs
/dev/mapper/system-root[/@/root] |-/root btrfs
/dev/mapper/system-home |-/home xfs
/dev/mapper/system-root[/@/opt] |-/opt btrfs
/dev/mapper/system-root[/@/boot/grub2/x86_64-efi] |-/boot/grub2/x86_64-efi btrfs
# grep '^fs ' ./var/lib/rear/layout/disklayout.conf
fs /dev/mapper/system-home /home xfs uuid=...
fs /dev/mapper/system-root / btrfs uuid=...
i.e. only one single btrfs filesystem,
cf. "SLES 15 SP 1 with default LVM and LUKS encryption and btrfs
structure" at
https://github.com/rear/rear/wiki/Test-Matrix-rear-2.6
mantriharish commented at 2021-03-09 12:36:¶
@jsmeix
rear -d -D mkbackup
RESCUE hedcb019:~ # rear -d -D mkbackup
Relax-and-Recover 2.6-git.4265.4b43f43.master / 2021-02-23
Running rear mkbackup (PID 5457 date 2021-03-09 12:33:46)
Using log file: /var/log/rear/rear-hedcb019.log
ERROR: The workflow mkbackup is not supported in the ReaR rescue/recovery system
Some latest log messages since the last called script 050_check_rear_recover_mode.sh:
2021-03-09 12:33:46.723566464 Including init/default/050_check_rear_recover_mode.sh
2021-03-09 12:33:46.724683402 Entering debugscript mode via 'set -x'.
Aborting due to an error, check /var/log/rear/rear-hedcb019.log for details
Exiting rear mkbackup (PID 5457) and its descendant processes ...
Running exit tasks
Terminated
RESCUE hedcb019:~ # rear -d -D mkrescue
Relax-and-Recover 2.6-git.4265.4b43f43.master / 2021-02-23
Running rear mkrescue (PID 5765 date 2021-03-09 12:35:00)
Using log file: /var/log/rear/rear-hedcb019.log
ERROR: The workflow mkrescue is not supported in the ReaR rescue/recovery system
Some latest log messages since the last called script 050_check_rear_recover_mode.sh:
2021-03-09 12:35:01.195197126 Including init/default/050_check_rear_recover_mode.sh
2021-03-09 12:35:01.196284177 Entering debugscript mode via 'set -x'.
Aborting due to an error, check /var/log/rear/rear-hedcb019.log for details
Exiting rear mkrescue (PID 5765) and its descendant processes ...
Running exit tasks
Terminated
mantriharish commented at 2021-03-09 12:37:¶
@jsmeix
RESCUE hedcb019:~ # findmnt -a -o SOURCE,TARGET,FSTYPE -t btrfs,ext2,ext3,ext4,
xfs,reiserfs,vfat
SOURCE TARGET FSTYPE
/dev/mapper/rootvg-rootvol[/@] /mnt/local btrfs
mantriharish commented at 2021-03-09 12:38:¶
@jsmeix
this is from the terminal ofr the rear recover system
mantriharish commented at 2021-03-09 12:41:¶
@jsmeix
just wanted to update you that i even updated my server from sles15sp1 to sles15sp2 and then took a rear backup of it using the below rear rpm package ie rear-2.6-142.git.4265.4b43f43.master.ppc64le
still i get the same error,,and another point this is a lpar running on power8 just for your info and the same rear backup works fine for sles12 sp2,sp3,sp4,sp5
mantriharish commented at 2021-03-09 12:47:¶
@jsmeix
i am also giving you the outputs from the server that the rear backup is
taken
and which i am trying ot restoer on another server
hedcb019:~ # lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,SIZE,MOUNTPOINT
NAME KNAME PKNAME TRAN TYPE FSTYPE SIZE MOUNTPOINT
/dev/sda /dev/sda disk mpath_member 50G
|-/dev/sda1 /dev/sda1 /dev/sda part mpath_member 6.8M
|-/dev/sda2 /dev/sda2 /dev/sda part LVM2_member 50G
`-/dev/mapper/mpatha /dev/dm-0 /dev/sda mpath 50G
|-/dev/mapper/mpatha-part1 /dev/dm-1 /dev/dm-0 part 6.8M
`-/dev/mapper/mpatha-part2 /dev/dm-2 /dev/dm-0 part LVM2_member 50G
|-/dev/mapper/rootvg-rootvol /dev/dm-3 /dev/dm-2 lvm btrfs 29.8G /
|-/dev/mapper/rootvg-swapvol /dev/dm-4 /dev/dm-2 lvm swap 2G [SWAP]
|-/dev/mapper/rootvg-expvol /dev/dm-5 /dev/dm-2 lvm btrfs 992M /exploit
|-/dev/mapper/rootvg-homevol /dev/dm-6 /dev/dm-2 lvm btrfs 992M /home
|-/dev/mapper/rootvg-iemvol /dev/dm-7 /dev/dm-2 lvm btrfs 3G /var/opt/BESClient
|-/dev/mapper/rootvg-optvol /dev/dm-8 /dev/dm-2 lvm btrfs 2G /opt
`-/dev/mapper/rootvg-varlogvol /dev/dm-9 /dev/dm-2 lvm btrfs 2G /var/log
/dev/sdb /dev/sdb disk mpath_member 50G
|-/dev/sdb1 /dev/sdb1 /dev/sdb part mpath_member 6.8M
|-/dev/sdb2 /dev/sdb2 /dev/sdb part LVM2_member 50G
`-/dev/mapper/mpatha /dev/dm-0 /dev/sdb mpath 50G
|-/dev/mapper/mpatha-part1 /dev/dm-1 /dev/dm-0 part 6.8M
`-/dev/mapper/mpatha-part2 /dev/dm-2 /dev/dm-0 part LVM2_member 50G
|-/dev/mapper/rootvg-rootvol /dev/dm-3 /dev/dm-2 lvm btrfs 29.8G /
|-/dev/mapper/rootvg-swapvol /dev/dm-4 /dev/dm-2 lvm swap 2G [SWAP]
|-/dev/mapper/rootvg-expvol /dev/dm-5 /dev/dm-2 lvm btrfs 992M /exploit
|-/dev/mapper/rootvg-homevol /dev/dm-6 /dev/dm-2 lvm btrfs 992M /home
|-/dev/mapper/rootvg-iemvol /dev/dm-7 /dev/dm-2 lvm btrfs 3G /var/opt/BESClient
|-/dev/mapper/rootvg-optvol /dev/dm-8 /dev/dm-2 lvm btrfs 2G /opt
`-/dev/mapper/rootvg-varlogvol /dev/dm-9 /dev/dm-2 lvm btrfs 2G /var/log
/dev/sdc /dev/sdc disk mpath_member 50G
|-/dev/sdc1 /dev/sdc1 /dev/sdc part mpath_member 6.8M
|-/dev/sdc2 /dev/sdc2 /dev/sdc part LVM2_member 50G
`-/dev/mapper/mpatha /dev/dm-0 /dev/sdc mpath 50G
|-/dev/mapper/mpatha-part1 /dev/dm-1 /dev/dm-0 part 6.8M
`-/dev/mapper/mpatha-part2 /dev/dm-2 /dev/dm-0 part LVM2_member 50G
|-/dev/mapper/rootvg-rootvol /dev/dm-3 /dev/dm-2 lvm btrfs 29.8G /
|-/dev/mapper/rootvg-swapvol /dev/dm-4 /dev/dm-2 lvm swap 2G [SWAP]
|-/dev/mapper/rootvg-expvol /dev/dm-5 /dev/dm-2 lvm btrfs 992M /exploit
|-/dev/mapper/rootvg-homevol /dev/dm-6 /dev/dm-2 lvm btrfs 992M /home
|-/dev/mapper/rootvg-iemvol /dev/dm-7 /dev/dm-2 lvm btrfs 3G /var/opt/BESClient
|-/dev/mapper/rootvg-optvol /dev/dm-8 /dev/dm-2 lvm btrfs 2G /opt
`-/dev/mapper/rootvg-varlogvol /dev/dm-9 /dev/dm-2 lvm btrfs 2G /var/log
/dev/sdd /dev/sdd disk mpath_member 50G
|-/dev/sdd1 /dev/sdd1 /dev/sdd part mpath_member 6.8M
|-/dev/sdd2 /dev/sdd2 /dev/sdd part LVM2_member 50G
`-/dev/mapper/mpatha /dev/dm-0 /dev/sdd mpath 50G
|-/dev/mapper/mpatha-part1 /dev/dm-1 /dev/dm-0 part 6.8M
`-/dev/mapper/mpatha-part2 /dev/dm-2 /dev/dm-0 part LVM2_member 50G
|-/dev/mapper/rootvg-rootvol /dev/dm-3 /dev/dm-2 lvm btrfs 29.8G /
|-/dev/mapper/rootvg-swapvol /dev/dm-4 /dev/dm-2 lvm swap 2G [SWAP]
|-/dev/mapper/rootvg-expvol /dev/dm-5 /dev/dm-2 lvm btrfs 992M /exploit
|-/dev/mapper/rootvg-homevol /dev/dm-6 /dev/dm-2 lvm btrfs 992M /home
|-/dev/mapper/rootvg-iemvol /dev/dm-7 /dev/dm-2 lvm btrfs 3G /var/opt/BESClient
|-/dev/mapper/rootvg-optvol /dev/dm-8 /dev/dm-2 lvm btrfs 2G /opt
`-/dev/mapper/rootvg-varlogvol /dev/dm-9 /dev/dm-2 lvm btrfs 2G /var/log
/dev/sr0 /dev/sr0 rom iso9660 648.3M
/dev/sr1 /dev/sr1 rom iso9660 5.2G
hedcb019:~ # findmnt -a -o SOURCE,TARGET,FSTYPE -t btrfs,ext2,ext3,ext4,xfs,reiserfs,vfat
SOURCE TARGET FSTYPE
/dev/mapper/rootvg-rootvol[/@/.snapshots/1/snapshot] / btrfs
/dev/mapper/rootvg-rootvol[/@/.snapshots] |-/.snapshots btrfs
/dev/mapper/rootvg-iemvol[/@] |-/var/opt/BESClient btrfs
/dev/mapper/rootvg-varlogvol[/@] |-/var/log btrfs
/dev/mapper/rootvg-homevol[/@] |-/home btrfs
/dev/mapper/rootvg-optvol[/@] |-/opt btrfs
/dev/mapper/rootvg-expvol[/@] `-/exploit btrfs
hedcb019:~ # grep '^fs ' /var/lib/rear/layout/disklayout.conf
fs /dev/mapper/rootvg-expvol /exploit btrfs uuid=082688f2-acf1-4dac-a783-449da8eeb3f6 label= options=rw,relatime,ssd,space_cache,subvolid=257,subvol=/@
fs /dev/mapper/rootvg-homevol /home btrfs uuid=36253a10-1f0e-418c-a433-a8f992d6ea5d label= options=rw,relatime,ssd,space_cache,subvolid=257,subvol=/@
fs /dev/mapper/rootvg-iemvol /var/opt/BESClient btrfs uuid=be8dd115-7220-4a8e-8ef6-9d8f7bae05ea label= options=rw,relatime,ssd,space_cache,subvolid=257,subvol=/@
fs /dev/mapper/rootvg-optvol /opt btrfs uuid=ab83dbb9-020a-46a6-8e7d-29ea3608f834 label= options=rw,relatime,ssd,space_cache,subvolid=257,subvol=/@
fs /dev/mapper/rootvg-rootvol / btrfs uuid=1f42b426-2a52-4672-ac5b-9e3693f9816a label= options=rw,relatime,ssd,space_cache,subvolid=259,subvol=/@/.snapshots/1/snapshot
fs /dev/mapper/rootvg-varlogvol /var/log btrfs uuid=db041ad2-0832-4280-8bc3-3083f02ff876 label= options=rw,relatime,ssd,space_cache,subvolid=257,subvol=/@
mantriharish commented at 2021-03-09 12:55:¶
@jsmeix
i forgot to give you the debug log file as reqeust above
debuglogfile.txt
mantriharish commented at 2021-03-10 05:48:¶
@jsmeix
Any luck on this issue do let me know i also open for a remote session if needed
jsmeix commented at 2021-03-10 10:31:¶
I will not do any remote access to ReaR user or SUSE customer machines.
Reason:
I never logged in on any ReaR user or SUSE customer machine before
and I won't start to do that here for the first time.
I have legal concerns with that.
What if something goes wrong and the ReaR user or SUSE customer
sues me because "I did something clearly obviously totally stupid"?
In particular when the machine at the ReaR user or SUSE customer
is not totally isolated from the rest of his machines like in this
case
where the storage seems to be accessed via SAN so this machine
is connected to storage that is likely not only accessible
by this one machine but also by other machines
perhaps even by production systems.
Experimenting with the storage is needed here
so arbitrary things could go wrong with the storage.
In particular I have neither experience with SAN storage specific
things
nor with multipath specific things nor with POWER architecture specific
things.
At SUSE we have people who are experienced in that areas.
Only I personally do not have experience in that areas.
jsmeix commented at 2021-03-10 10:36:¶
@mantriharish
I need two ReaR debug log files as described in the section
To analyze and debug a "rear recover" failure the following information is mandatory
in
https://en.opensuse.org/SDB:Disaster_Recovery#Debugging_issues_with_Relax-and-Recover
Yesterday I enhanced that section again to make it more clear from what
system
("original system" versus "ReaR recovery system"/"replacement system")
what information is needed.
mantriharish commented at 2021-03-10 12:44:¶
@jsmeix
you are looking for any additional log files from my end...yesterday i
had provided ,,is there something still missing from my end
mantriharish commented at 2021-03-10 12:45:¶
@jsmeix
ReaR version ("/usr/sbin/rear -V")
Operating system version ("cat /etc/os-release" or "lsb_release -a" or
"cat /etc/rear/os.conf")
ReaR configuration files ("cat /etc/rear/local.conf" and/or "cat
/etc/rear/site.conf")
Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest
or PoverVM LPAR) of the original system and if different also what is
used as replacement hardware (or virtual machine)
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM
device) of the original system (must be same for what is used as
replacement system)
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO
or Petitboot) on the original system (must be same for what is used on
the replacement hardware)
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or
multipath (DM or NVMe) on the original system and if a bit different
also what is used on the replacement hardware (should be as same as
possible for what is used as replacement storage)
The output of "lsblk -ipo
NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,SIZE,MOUNTPOINT" on the original
system
The output of "findmnt -a -o SOURCE,TARGET,FSTYPE -t
btrfs,ext2,ext3,ext4,xfs,reiserfs,vfat" on the original system
Debug log file of "rear -d -D mkbackup" or "rear -d -D mkrescue" (in
/var/log/rear/) that matches the "rear recover" failure (i.e. debug log
from the original system of the "rear -d -D mkbackup" or "rear -d -D
mkrescue" command that created the ReaR recovery system where "rear
recover" failed)
Debug log file of "rear -d -D recover" (in /var/log/rear/) from the ReaR
recovery system where "rear recover" failed (see above how to save the
log file out of the ReaR recovery system)
Contents of the /var/lib/rear/ directory and in its sub-directories from
the ReaR recovery system where "rear recover" failed (see above how to
save files out of the ReaR recovery system)
mantriharish commented at 2021-03-10 12:49:¶
i am reuploading the details you have requestd for let me know if you need any additional logs
mantriharish commented at 2021-03-11 07:07:¶
@jsmeix
Any update on the query did you get any break through
mantriharish commented at 2021-03-11 07:08:¶
@jsmeix
Please let me know if you have any additional queries or logs from my end
mantriharish commented at 2021-03-12 06:44:¶
@jsmeix
Any luck on the investigation from your end on this issue
mantriharish commented at 2021-03-15 06:02:¶
@jsmeix
Hope you doing fine just wanted to know if you had any breakthrough on my request
mantriharish commented at 2021-03-16 08:53:¶
@jsmeix
Any breakthough in this case,,,)
jsmeix commented at 2021-03-16 10:15:¶
@mantriharish
because things work for me with btrfs on SLE15
on usual x86_64 (virtual) hardware with usual (virtual) harddisk
storage,
cf.
https://github.com/rear/rear/issues/2584#issuecomment-793822658
while in contrast
this issue happens on specific hardware (POWER P9 9009-42A--LPAR)
with special storage (SAN ---FCS----MULTIPAHT) that I neither have
here
where I am (homeoffice) nor where I have personal experience with,
there is not much what I could do only on my own to find out
what the root cause of this issue is in your particular case.
Therefore I would like to suggest that you continue only via
your already existing SUSE internal support issue because
at SUSE we have people who are experienced in that areas,
cf.
https://github.com/rear/rear/issues/2584#issuecomment-795216294
When the root cause of this issue is found at SUSE and
a possible workaround or bugfix in ReaR is developed
I will continue here and describe the root cause
and a possible workaround (if exists)
and/or provide a GitHub pull request with a fix (if exists).
mantriharish commented at 2021-03-16 10:20:¶
@jsmeix
Thanks for your reply,,infact as told you i have opened the call with suse and they say they have asked their development team on this and said wil com back to me,,but i have not go any inputs on the same form them till now,,do you have some contacts who can help me on this or can you please have a check if the development team did received this request from support
jsmeix commented at 2021-03-16 10:49:¶
@mantriharish
for official SUSE support communication you need to use
(only) the official SUSE support communication channels.
I can neither tell you what those channels are nor how to use them
because that depends on your particular support contract with SUSE.
I do not work in the SUSE support department so I do not know
about your particular support contract with SUSE.
In general I cannot provide you an official SUSE support reply here
via this public accessible ReaR upstream GitHub issue.
github-actions commented at 2021-05-16 02:40:¶
Stale issue message
[Export of Github issue for rear/rear.]