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
HP Superdome-X servers using multipath an booting from SAN not backing up de ROOT filesystem! #882
Comments
The code that uses the findmnt command is from me I do not run RHEL (and I do not know what is special on RHEL) @didacog @didacog andtags which works o.k. for me but one has to write < as HTML < Perhaps there is something even better how to specify preformatted texts in GitHub? |
Ok I will prepare the pull request. this is the code to change, just one findmnt option: /usr/share/rear/layout/save/GNU/Linux/23_filesystem_layout.sh Change this line: read_filesystems_command="$findmnt_command -nrv -o SOURCE,TARGET,FSTYPE,OPTIONS -t $supported_filesystems" to: read_filesystems_command="$findmnt_command -mnrv -o SOURCE,TARGET,FSTYPE,OPTIONS -t $supported_filesystems" I will also check if any modification needed for this other issue: 2016-06-16 13:22:34.103712191 Could not determine start of partition vvbootp1. resulting in /var/lib/rear/layout/disklayout.conf: part /dev/mapper/vvboot 536870912 unknown rear-noname boot /dev/mapper/vvbootp1 And provide a pull request with all modifications needed. Thanks! Didac |
I changed the initial comment to andtags and now I can better read it. On very first glance I do not like to force findmnt command to use /etc/mtab instead of /proc/self/mountinfo because think using /etc/mtab is an indirection (cf. RFC1925 6a) @didacog |
On my SLES12-SP1 system with its default btrfs structure What I did: # cat /etc/os-release NAME="SLES" VERSION="12-SP1" VERSION_ID="12.1" PRETTY_NAME="SUSE Linux Enterprise Server 12 SP1" ... # /usr/bin/findmnt -mnrv -o SOURCE,TARGET,FSTYPE,OPTIONS -t ext2,ext3,ext4,vfat,xfs,reiserfs,btrfs >/tmp/findmnt-mnrv # /usr/bin/findmnt -nrv -o SOURCE,TARGET,FSTYPE,OPTIONS -t ext2,ext3,ext4,vfat,xfs,reiserfs,btrfs >/tmp/findmnt-nrv # diff -s /tmp/findmnt-nrv /tmp/findmnt-mnrv Files /tmp/findmnt-nrv and /tmp/findmnt-mnrv are identical |
Nevertheless I need to inspect what the actual difference is |
@jsmeix you are really fast! ;) I think this will be the same behaviour as using mount command if findmnt is not present, and should work. I'm now deeping with the other issue with partition layouts and after that I will provide a pull request. Thanks! |
@jsmeix i found this post regarding /proc/self/mounts vs /proc/self/mountinfo: |
If it is really the exact same behaviour as the old mount command See also my comment regarding "man 8 mount" On the other hand perhaps using "findmnt -m..." |
@didacog Obviously I cannot do such a test myself because I do not Such a test would help a lot to ensure that also btrfs subvolumes I never tested rear myself with SAN and multipath. I blindly guess that general support when the root filesystem |
@didacog I do not yet fully understand what is meant in /proc/self/mountinfo is the most authoritative source to check your mounts. /proc/mounts is a deprecated source to check the status of your mounts. ... /proc/mounts symlinks to /proc/self/mounts As far as I understand it this means that Accordingly it seems "findmnt -m..." |
I think that with the root partition on mpath device, the problem is when kernel loading the root partiton booting from SAN, this partition has not yet the mpath alias defined in kernel and keeps its WWN name on the /proc/self/mountinfo file. Maybe an exeption when booting from SAN? the problem is that if not properly identified with this name, root filesystem is not present in disklayout file and does not backup of (/). I will figure out other solutions and use this as workarround in the meantime, and if is possible i will test with SLES, but I cannot promise because those SuperdomeX are not mine :P |
@jsmeix This case is not with Boot from SAN on SuperdomeX but same output from findmnt command with -m option with btrfs subvolumes on SLES11 SP3: $ findmnt -nrv -o SOURCE,TARGET,FSTYPE,OPTIONS -t btrfs $ findmnt -mnrv -o SOURCE,TARGET,FSTYPE,OPTIONS -t btrfs Also I've seen that /etc/mtab is a softlink to /proc/self/mounts in SLES but not in RHEL. SLES: RHEL6: Maybe we need to use a different approach for each OS. |
In general I am agianst using different approaches In contrast I prefer to use different approaches I.e. I am against code like case "$OS_VENDOR" in (SUSE_LINUX) do_this ;; (RedHatEnterpriseServer) do_that ;; (*) do_default ;; esac In contrast I prefer code like if CONDITION ; then do_this else do_that fi where CONDITION is something real that can be directly For example I tried to implement my btrfs support code |
@didacog First to make "fs" entries in disklayout.conf. Afterwards to make "btrfs..." entries in disklayout.comf. For the first usage (make "fs" entries) see my comment # The only difference is that the traditional mount command output has the list of options in parenthesis. so that here - at last for now - using "findmnt -m" In contrast for the other usages (make "btrfs..." entries) Therefore to make make "btrfs..." entries I assume |
Ok, maybe tomorrow I can try to run a backup with this modified on one of the development SLES servers with btrfs subvolumes and check if working ok with findmnt -m. I guess this should work because, as you can see on the SLES outputs I provided are the same and the origin file format Is very different, but anyway, tomorrow I would clear those doubts :P |
@didacog According to what I wrote above in #882 (comment) @didacog device WWN from SAN instead of the mpath alias name Colud you explain (or provide an URL to explanatory info) Via quick "Googling" I found Perhaps the actually right future-proof solution is Must each 'WWID' or 'WWN' have exactly one Perhaps there is already some ready-to-use command line tool |
I've tested with SLES and here my results: ... SLES11 SP3 (rear log): 2016-06-17 10:57:04.940394305 Begin saving filesystem layout 2016-06-17 10:57:04.943144580 Saving filesystem layout (using the findmnt command). /usr/share/rear/layout/save/GNU/Linux/23_filesystem_layout.sh: line 123: dosfslabel: command not found findmnt: unknown column: FSROOT 2016-06-17 10:57:05.103735053 End saving filesystem layout ... I've tested this on shell: ######################################## # Mounted btrfs subvolumes: if test -x "$findmnt_command" ; then read_mounted_btrfs_subvolumes_command="$findmnt_command -nrv -o SOURCE,TARGET,OPTIONS,FSROOT -t btrfs" else read_mounted_btrfs_subvolumes_command="mount -t btrfs | cut -d ' ' -f 1,3,6" fi SLES: $ findmnt -nrv -o SOURCE,TARGET,OPTIONS,FSROOT -t btrfs findmnt: unknown column: FSROOT RHEL: $ findmnt -nrv -o SOURCE,TARGET,OPTIONS,FSROOT -t btrfs findmnt: unknown column: FSROOT Seems this command is not working at this time. the resulting disklayout have same output format (because in fact the first findmnt command is getting the fs list and the specific btrfs command is not working) supported_filesystems="ext2,ext3,ext4,vfat,xfs,reiserfs,btrfs" read_filesystems_command="$findmnt_command -mnrv -o SOURCE,TARGET,FSTYPE,OPTIONS -t $supported_filesystems" findmnt -m ... is working also with BTRFS subvols and the dedicated btrfs command is not working. Look at disklayout outputs: # grep btrfssnap disklayout.conf (with findmnt -m ... ) # Format: btrfssnapshotsubvol #btrfssnapshotsubvol /dev/sda4 / 276 @/.snapshots/1/snapshot #btrfssnapshotsubvol /dev/sda4 / 277 @/opt/.snapshots/1/snapshot #btrfssnapshotsubvol /dev/sda4 / 283 @/.snapshots/4/snapshot #btrfssnapshotsubvol /dev/sda4 / 284 @/.snapshots/5/snapshot #btrfssnapshotsubvol /dev/sda4 / 470 @/.snapshots/98/snapshot #btrfssnapshotsubvol /dev/sda4 / 471 @/opt/.snapshots/96/snapshot #btrfssnapshotsubvol /dev/sda4 / 608 @/.snapshots/167/snapshot #btrfssnapshotsubvol /dev/sda4 / 609 @/.snapshots/168/snapshot #btrfssnapshotsubvol /dev/sda4 / 610 @/.snapshots/169/snapshot #btrfssnapshotsubvol /dev/sda4 / 611 @/.snapshots/170/snapshot #btrfssnapshotsubvol /dev/sda4 / 1595 @/.snapshots/662/snapshot #btrfssnapshotsubvol /dev/sda4 / 1596 @/opt/.snapshots/656/snapshot #btrfssnapshotsubvol /dev/sda4 / 3036 @/.snapshots/1382/snapshot #btrfssnapshotsubvol /dev/sda4 / 3037 @/opt/.snapshots/1376/snapshot #btrfssnapshotsubvol /dev/sda4 / 4261 @/.snapshots/1993/snapshot #btrfssnapshotsubvol /dev/sda4 / 4262 @/.snapshots/1994/snapshot #btrfssnapshotsubvol /dev/sda4 / 4263 @/.snapshots/1995/snapshot #btrfssnapshotsubvol /dev/sda4 / 4265 @/.snapshots/1996/snapshot #btrfssnapshotsubvol /dev/sda4 / 4532 @/.snapshots/2130/snapshot #btrfssnapshotsubvol /dev/sda4 / 4533 @/opt/.snapshots/2120/snapshot #btrfssnapshotsubvol /dev/sda4 / 4820 @/.snapshots/2274/snapshot #btrfssnapshotsubvol /dev/sda4 / 4821 @/opt/.snapshots/2264/snapshot #btrfssnapshotsubvol /dev/sda4 / 4868 @/.snapshots/2298/snapshot #btrfssnapshotsubvol /dev/sda4 / 4869 @/opt/.snapshots/2288/snapshot #btrfssnapshotsubvol /dev/sda4 / 4916 @/.snapshots/2322/snapshot #btrfssnapshotsubvol /dev/sda4 / 4917 @/opt/.snapshots/2312/snapshot #btrfssnapshotsubvol /dev/sda4 / 4964 @/.snapshots/2346/snapshot #btrfssnapshotsubvol /dev/sda4 / 4965 @/opt/.snapshots/2336/snapshot #btrfssnapshotsubvol /dev/sda4 / 5012 @/.snapshots/2370/snapshot #btrfssnapshotsubvol /dev/sda4 / 5013 @/opt/.snapshots/2360/snapshot #btrfssnapshotsubvol /dev/sda4 / 5060 @/.snapshots/2394/snapshot #btrfssnapshotsubvol /dev/sda4 / 5061 @/opt/.snapshots/2384/snapshot #btrfssnapshotsubvol /dev/sda4 / 5108 @/.snapshots/2418/snapshot #btrfssnapshotsubvol /dev/sda4 / 5109 @/opt/.snapshots/2408/snapshot ... ... $ grep btrfssnap disklayout.conf.orig (without findmnt -m ... ) # Format: btrfssnapshotsubvol #btrfssnapshotsubvol /dev/sda4 / 276 @/.snapshots/1/snapshot #btrfssnapshotsubvol /dev/sda4 / 277 @/opt/.snapshots/1/snapshot #btrfssnapshotsubvol /dev/sda4 / 283 @/.snapshots/4/snapshot #btrfssnapshotsubvol /dev/sda4 / 284 @/.snapshots/5/snapshot #btrfssnapshotsubvol /dev/sda4 / 470 @/.snapshots/98/snapshot #btrfssnapshotsubvol /dev/sda4 / 471 @/opt/.snapshots/96/snapshot #btrfssnapshotsubvol /dev/sda4 / 608 @/.snapshots/167/snapshot #btrfssnapshotsubvol /dev/sda4 / 609 @/.snapshots/168/snapshot #btrfssnapshotsubvol /dev/sda4 / 610 @/.snapshots/169/snapshot #btrfssnapshotsubvol /dev/sda4 / 611 @/.snapshots/170/snapshot #btrfssnapshotsubvol /dev/sda4 / 1595 @/.snapshots/662/snapshot #btrfssnapshotsubvol /dev/sda4 / 1596 @/opt/.snapshots/656/snapshot #btrfssnapshotsubvol /dev/sda4 / 3036 @/.snapshots/1382/snapshot #btrfssnapshotsubvol /dev/sda4 / 3037 @/opt/.snapshots/1376/snapshot #btrfssnapshotsubvol /dev/sda4 / 4261 @/.snapshots/1993/snapshot #btrfssnapshotsubvol /dev/sda4 / 4262 @/.snapshots/1994/snapshot #btrfssnapshotsubvol /dev/sda4 / 4263 @/.snapshots/1995/snapshot #btrfssnapshotsubvol /dev/sda4 / 4265 @/.snapshots/1996/snapshot #btrfssnapshotsubvol /dev/sda4 / 4532 @/.snapshots/2130/snapshot #btrfssnapshotsubvol /dev/sda4 / 4533 @/opt/.snapshots/2120/snapshot #btrfssnapshotsubvol /dev/sda4 / 4772 @/.snapshots/2250/snapshot #btrfssnapshotsubvol /dev/sda4 / 4773 @/opt/.snapshots/2240/snapshot #btrfssnapshotsubvol /dev/sda4 / 4820 @/.snapshots/2274/snapshot #btrfssnapshotsubvol /dev/sda4 / 4821 @/opt/.snapshots/2264/snapshot #btrfssnapshotsubvol /dev/sda4 / 4868 @/.snapshots/2298/snapshot #btrfssnapshotsubvol /dev/sda4 / 4869 @/opt/.snapshots/2288/snapshot #btrfssnapshotsubvol /dev/sda4 / 4916 @/.snapshots/2322/snapshot #btrfssnapshotsubvol /dev/sda4 / 4917 @/opt/.snapshots/2312/snapshot #btrfssnapshotsubvol /dev/sda4 / 4964 @/.snapshots/2346/snapshot #btrfssnapshotsubvol /dev/sda4 / 4965 @/opt/.snapshots/2336/snapshot #btrfssnapshotsubvol /dev/sda4 / 5012 @/.snapshots/2370/snapshot #btrfssnapshotsubvol /dev/sda4 / 5013 @/opt/.snapshots/2360/snapshot #btrfssnapshotsubvol /dev/sda4 / 5060 @/.snapshots/2394/snapshot ... ... Regarding to WWN, yes is WWID, the unique name/ID of a Storage LUN. The problem is that after the multipath is loaded to the kernel and applied all aliases, /dev/mapper/WWIDpX no longer exists on system, only the alias /dev/mapper/vvbootp4. This is the cause rear is not able to get (/) information from system getting findmnt info from /proc/self/mountinfo because the block device is trying to get info no longer exists. |
@didacog You are right. # findmnt -nrv -o SOURCE,TARGET,OPTIONS,FSROOT findmnt: unknown column: FSROOT The reason why this was not noticed up to now is On SLE12 findmnt knows about FSROOT I will provide a fix soon via #883 |
@jsmeix What about -m option? did you test it on SLES12? On SLES11 with btrfs subvols the output with or without (-m) is the same. Anyway I cannot test it with SLES12 and not sure if something changes with FSROOT option. |
I merged #884 Furthermore with #884 @didacog I did not yet test whether or not SLE11 with btrfs |
Ok, I will test it and provide some feedback ASAP ;) |
A quick test with SLE11-SP4 with btrfs During initial installation of SLE11-SP4 I got this partitioning: # parted -l Model: ATA QEMU HARDDISK (scsi) Disk /dev/sda: 21.5GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 1049kB 165MB 164MB primary ext3 boot, type=83 2 165MB 1735MB 1571MB primary linux-swap(v1) type=82 3 1735MB 21.5GB 19.7GB primary btrfs type=83 and that btrfs subvolumes: # btrfs subvolume list -a / ID 256 gen 194 top level 5 path /@ ID 258 gen 195 top level 256 path @/tmp ID 259 gen 166 top level 256 path @/opt ID 260 gen 166 top level 256 path @/srv ID 261 gen 126 top level 256 path @/var/crash ID 262 gen 209 top level 256 path @/var/spool ID 263 gen 208 top level 256 path @/var/log ID 264 gen 208 top level 256 path @/var/run ID 265 gen 166 top level 256 path @/var/tmp ID 268 gen 195 top level 256 path @/.snapshots I used this /etc/rear/local.conf OUTPUT=ISO BACKUP=NETFS BACKUP_OPTIONS="nfsvers=3,nolock" BACKUP_URL=nfs://10.160.4.244/nfs NETFS_KEEP_OLD_BACKUP_COPY=yes BACKUP_PROG_INCLUDE=( '/var/tmp/*' '/var/run/*' '/var/spool/*' '/var/log/*' '/var/crash/*' '/tmp/*' '/srv/*' '/opt/*' ) SSH_ROOT_PASSWORD="rear" USE_DHCLIENT="yes" KEEP_BUILD_DIR="" I did not fully verify it all is really correct after "rear recover" |
@didacog I wonder why you cannot test it with SLES12? We (i.e. SUSE) have SLE12 installation images available Furthermore there is the new public SUSE Beta Program, see |
Tested on SLES12SP1. ;) findmnt command shows same output with or without (-m) option. In this case, maybe using (-mnrv) on all cases could be a good solution. here the evidence: linux-hxww:~ # lsb_release -a LSB Version: n/a Distributor ID: SUSE LINUX Description: SUSE Linux Enterprise Server 12 SP1 Release: 12.1 Codename: n/a linux-hxww:~ # findmnt -nrv -o SOURCE,TARGET,OPTIONS,FSROOT -t btrfs /dev/sda2 / rw,relatime,space_cache,subvolid=257,subvol=/@ /@ /dev/sda2 /var/tmp rw,relatime,space_cache,subvolid=275,subvol=/@/var/tmp /@/var/tmp /dev/sda2 /var/lib/mariadb rw,relatime,space_cache,subvolid=268,subvol=/@/var/lib/mariadb /@/var/lib/mariadb /dev/sda2 /var/spool rw,relatime,space_cache,subvolid=274,subvol=/@/var/spool /@/var/spool /dev/sda2 /var/lib/libvirt/images rw,relatime,space_cache,subvolid=266,subvol=/@/var/lib/libvirt/images /@/var/lib/libvirt/images /dev/sda2 /var/opt rw,relatime,space_cache,subvolid=273,subvol=/@/var/opt /@/var/opt /dev/sda2 /var/log rw,relatime,space_cache,subvolid=272,subvol=/@/var/log /@/var/log /dev/sda2 /var/lib/pgsql rw,relatime,space_cache,subvolid=271,subvol=/@/var/lib/pgsql /@/var/lib/pgsql /dev/sda2 /var/lib/named rw,relatime,space_cache,subvolid=270,subvol=/@/var/lib/named /@/var/lib/named /dev/sda2 /var/lib/mysql rw,relatime,space_cache,subvolid=269,subvol=/@/var/lib/mysql /@/var/lib/mysql /dev/sda2 /var/lib/mailman rw,relatime,space_cache,subvolid=267,subvol=/@/var/lib/mailman /@/var/lib/mailman /dev/sda2 /var/crash rw,relatime,space_cache,subvolid=265,subvol=/@/var/crash /@/var/crash /dev/sda2 /usr/local rw,relatime,space_cache,subvolid=264,subvol=/@/usr/local /@/usr/local /dev/sda2 /tmp rw,relatime,space_cache,subvolid=263,subvol=/@/tmp /@/tmp /dev/sda2 /opt rw,relatime,space_cache,subvolid=261,subvol=/@/opt /@/opt /dev/sda2 /srv rw,relatime,space_cache,subvolid=262,subvol=/@/srv /@/srv /dev/sda2 /home rw,relatime,space_cache,subvolid=260,subvol=/@/home /@/home /dev/sda2 /boot/grub2/x86_64-efi rw,relatime,space_cache,subvolid=259,subvol=/@/boot/grub2/x86_64-efi /@/boot/grub2/x86_64-efi /dev/sda2 /boot/grub2/i386-pc rw,relatime,space_cache,subvolid=258,subvol=/@/boot/grub2/i386-pc /@/boot/grub2/i386-pc linux-hxww:~ # findmnt -mnrv -o SOURCE,TARGET,OPTIONS,FSROOT -t btrfs /dev/sda2 / rw,relatime,space_cache,subvolid=257,subvol=/@ /@ /dev/sda2 /var/tmp rw,relatime,space_cache,subvolid=275,subvol=/@/var/tmp /@/var/tmp /dev/sda2 /var/lib/mariadb rw,relatime,space_cache,subvolid=268,subvol=/@/var/lib/mariadb /@/var/lib/mariadb /dev/sda2 /var/spool rw,relatime,space_cache,subvolid=274,subvol=/@/var/spool /@/var/spool /dev/sda2 /var/lib/libvirt/images rw,relatime,space_cache,subvolid=266,subvol=/@/var/lib/libvirt/images /@/var/lib/libvirt/images /dev/sda2 /var/opt rw,relatime,space_cache,subvolid=273,subvol=/@/var/opt /@/var/opt /dev/sda2 /var/log rw,relatime,space_cache,subvolid=272,subvol=/@/var/log /@/var/log /dev/sda2 /var/lib/pgsql rw,relatime,space_cache,subvolid=271,subvol=/@/var/lib/pgsql /@/var/lib/pgsql /dev/sda2 /var/lib/named rw,relatime,space_cache,subvolid=270,subvol=/@/var/lib/named /@/var/lib/named /dev/sda2 /var/lib/mysql rw,relatime,space_cache,subvolid=269,subvol=/@/var/lib/mysql /@/var/lib/mysql /dev/sda2 /var/lib/mailman rw,relatime,space_cache,subvolid=267,subvol=/@/var/lib/mailman /@/var/lib/mailman /dev/sda2 /var/crash rw,relatime,space_cache,subvolid=265,subvol=/@/var/crash /@/var/crash /dev/sda2 /usr/local rw,relatime,space_cache,subvolid=264,subvol=/@/usr/local /@/usr/local /dev/sda2 /tmp rw,relatime,space_cache,subvolid=263,subvol=/@/tmp /@/tmp /dev/sda2 /opt rw,relatime,space_cache,subvolid=261,subvol=/@/opt /@/opt /dev/sda2 /srv rw,relatime,space_cache,subvolid=262,subvol=/@/srv /@/srv /dev/sda2 /home rw,relatime,space_cache,subvolid=260,subvol=/@/home /@/home /dev/sda2 /boot/grub2/x86_64-efi rw,relatime,space_cache,subvolid=259,subvol=/@/boot/grub2/x86_64-efi /@/boot/grub2/x86_64-efi /dev/sda2 /boot/grub2/i386-pc rw,relatime,space_cache,subvolid=258,subvol=/@/boot/grub2/i386-pc /@/boot/grub2/i386-pc linux-hxww:~ # findmnt -nrv -o SOURCE,TARGET,OPTIONS,FSROOT -t btrfs > findmnt.out linux-hxww:~ # findmnt -mnrv -o SOURCE,TARGET,OPTIONS,FSROOT -t btrfs > findmnt-m.out linux-hxww:~ # diff findmnt.out findmnt-m.out |
Tomorrow I will test to recover on SLES12 with your latest code for the FSROOT option, but anyway the findmnt (-m ) should be on BTRFS section also, because if not, in case of BTRFS with BOOT from SAN it will fail with same issue. With my last test the output is the same on both cases. I will open an issue for them also together with the pull request. Regards, |
@didacog In this particular case: |
Ok, tomorrow I will submit a new pull request with those changes properly documented. Regards, |
Hi @jsmeix, I've submitted a new pull request #903 solving findmnt problems (findmnt -m). I've tested it on SLES 12 and worked. Also meet a problem with chattr missing on rescue image. Should be solved with the pull request. I had problems with usr/share/rear/finalize/Linux-i386/23_run_efibootmgr.sh. But is solved in 1.18 with this code: if [[ ${Dev/mapper//} != $Dev ]] ; then # we have 'mapper' in devname # we only expect mpath_partX or mpathpX or mpath-partX case $Disk in (*p) Disk=${Disk%p} ;; (*-part) Disk=${Disk%-part} ;; (*_part) Disk=${Disk%_part} ;; (*) Log "Unsupported kpartx partition delimiter for $Dev" esac fi Regards, |
@didacog Regarding your "problems with ... 23_run_efibootmgr.sh" I think it would be better when you submit a new separated In particular because I am not at all an expert regarding Or perhaps just do a separated GitHub pull request that |
@didacog In current rear master code your mentioned code FYI: "git blame" shows for 23_run_efibootmgr.sh @didacog I.e. is this particular issue fixed for you |
@jsmeix Yes you can close this issue. Thanks! ;) |
Relax-and-Recover (rear) Issue Template
Please fill in the following items before submitting a new issue:
Relax-and-Recover 1.17.2 / Git
LSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch
Distributor ID: RedHatEnterpriseServer
Description: Red Hat Enterprise Linux Server release 6.6 (Santiago)
Release: 6.6
Codename: Santiago
We are playing with new HP Superdome-X servers. These brand new servers are using multipath an booting from SAN.
On disk layout collection never gets info from root filesystem (/) but for other partitions in same device collects all info with no problems. The problem is that is not backing up de ROOT filesystem!
There is an issue with this file: /usr/share/rear/layout/save/GNU/Linux/23_filesystem_layout.sh
this line:
In this case is informing the device WWN from SAN instead of the mpath alias name used in all rear scripts.
Proposal:
/usr/share/rear/layout/save/GNU/Linux/23_filesystem_layout.sh
Change this line:
to:
This will force findmnt command to use /etc/mtab instead of /proc/self/mountinfo and provide the correct info resulting in the correct disklayout file:
I've tested it and now is getting the correct info, but prior to sending a pull request I would ask if you guys have any concern about this modification.
Kind Regards!
Didac
The text was updated successfully, but these errors were encountered: