You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When there are two disks /dev/sda and /dev/sdb with same size
"rear recover" goes into MIGRATION_MODE
(which is right to be on the safe side):
Comparing disks
Ambiguous possible target disks need manual configuration (more than one with same size found)
Switching to manual disk layout configuration
Using /dev/sda (same name and same size) for recreating /dev/sda
Current disk mapping table (source -> target):
/dev/sda /dev/sda
But when that identical mapping "/dev/sda => /dev/sda" is used
then files like disklayout.conf and during finalize stage even restored files
get needlessly modified (hopefully usually with actually identical modification
but that lots of needlessly done sed magic might result unwanted changes):
Applying disk layout mappings in /var/lib/rear/layout/disk_mappings to certain restored files...
The original restored files get saved in var/lib/rear/saved_original_files/ (in /mnt/local)
Applied disk layout mappings to restored 'boot/grub2/grub.cfg' (in /mnt/local)
Applied disk layout mappings to restored 'boot/grub2/device.map' (in /mnt/local)
Applied disk layout mappings to restored 'etc/sysconfig/bootloader' (in /mnt/local)
Applied disk layout mappings to restored 'etc/fstab' (in /mnt/local)
Applied disk layout mappings to restored 'etc/mtools.conf' (in /mnt/local)
Applied disk layout mappings to restored 'etc/smartd.conf' (in /mnt/local)
Applied disk layout mappings to restored 'etc/sysconfig/smartmontools' (in /mnt/local)
One can see that since #1843 is merged
but it happened all the time (only silently and without saving original files).
I will try to detect a completely identical mapping
i.e. all entries in /var/lib/rear/layout/disk_mappings must be an identity map like
jsmeix
changed the title
In finalize stage restored files get modified for identical mapping /dev/sda => /dev/sda
Files (also restored files) get needlessly modified for identical mapping /dev/sda => /dev/sda
Jun 29, 2018
…B2_installation_for_ppc64le
Fixed, simplified and enhanced GRUB2 installation for PPC64/PPC64LE
in the same way as it was already done for x86 architecture,
cf. #1843
and #1828
so that the code in finalize/Linux-ppc64le/620_install_grub2.sh
is aligned with the code in finalize/Linux-i386/620_install_grub2.sh
as far as possible.
Additionally the new is_completely_identical_layout_mapping function
detects if a completely identical mapping and is used
to not run the apply_layout_mappings function
when there is a completely identical mapping
cf. #1847
Using current master code.
When there are two disks /dev/sda and /dev/sdb with same size
"rear recover" goes into MIGRATION_MODE
(which is right to be on the safe side):
But when that identical mapping "/dev/sda => /dev/sda" is used
then files like disklayout.conf and during finalize stage even restored files
get needlessly modified (hopefully usually with actually identical modification
but that lots of needlessly done
sed
magic might result unwanted changes):One can see that since #1843 is merged
but it happened all the time (only silently and without saving original files).
I will try to detect a completely identical mapping
i.e. all entries in /var/lib/rear/layout/disk_mappings must be an identity map like
and in this case all what belongs to /var/lib/rear/layout/disk_mappings
can be skipped.
The text was updated successfully, but these errors were encountered: