+++ This bug was initially created as a clone of Bug #2172589 +++ Description of problem: The s390x architecture needs some unique handling of disks (called DASDs - Direct Access Storage Devices) during layout restoration. The DASDs need to get formatted (at low level), unless they are formatted already, before they can be partitioned. Formatting of the disks is controlled by the dasdfmt directive in the disklayout.conf file. This directive is emitted for all dasds, regardless of whether they should be included in the layout. While there is component exclusion code that comments out the "disk" lines for unused disks automatically, the dasdfmt lines for unused disks stay in the layout file, which later causes the unused disks to be reformatted unconditionally. Crucially, this includes the disk with the backup (one must use network backup storage because of this). As a result, if users have disks that ReaR is not supposed to touch (neither backup not restore), the recovery procedure will erase them. Version-Release number of selected component (if applicable): 2.6-16.el9 (and anything earlier) How reproducible: well reproducible, but needs multiple disks Steps to Reproduce: 1. get a s390x machine with multiple disks and install RHEL only on one disk (e.g. dasda) 2. partition (fdasd -a) and create a filesystem on the second disk (e.g. dasdb) but do not mount it 3. perform a ReaR backup 4. recover the system with ReaR Actual results: Filesystem on dasdb is gone Expected results: Filesystem on dasdb should have survived - ReaR does not include dasdb in the recreated layout as it is not used (filesystem is not mounted).
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (rear bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:2900