RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2172589 - ReaR formats all dasds on s390x
Summary: ReaR formats all dasds on s390x
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: rear
Version: 9.0
Hardware: s390x
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Pavel Cahyna
QA Contact: David Jež
Šárka Jana
URL:
Whiteboard:
Depends On:
Blocks: 2172605
TreeView+ depends on / blocked
 
Reported: 2023-02-22 15:50 UTC by Pavel Cahyna
Modified: 2023-05-09 09:24 UTC (History)
3 users (show)

Fixed In Version: rear-2.6-17.el9
Doc Type: Bug Fix
Doc Text:
.ReaR handles excluded DASDs on the IBM Z architecture correctly Previously on the IBM Z architecture, ReaR reformatted all connected Direct Access Storage Devices (DASD) during the recovery process, including those DASDs that users excluded from the saved layout and did not intend to restore their content. As a consequence, if you excluded some DASDs from the saved layout, their data were lost during system recovery. With this update, ReaR no longer formats excluded DASDs during system recovery, including the device from which the ReaR rescue system was booted (using the zIPL bootloader). You are also prompted to confirm the DASD formatting script before ReaR reformats DASDs. This ensures that the data on excluded DASDs survive a system recovery.
Clone Of:
: 2172605 (view as bug list)
Environment:
Last Closed: 2023-05-09 07:53:44 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github rear rear pull 2943 0 None open s390x (IBM Z) disk formatting fixes 2023-02-22 15:50:28 UTC
Red Hat Issue Tracker RHELPLAN-149690 0 None None None 2023-02-22 15:52:35 UTC
Red Hat Product Errata RHBA-2023:2414 0 None None None 2023-05-09 07:53:59 UTC

Description Pavel Cahyna 2023-02-22 15:50:28 UTC
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).

Comment 11 errata-xmlrpc 2023-05-09 07:53:44 UTC
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:2414


Note You need to log in before you can comment on or make changes to this bug.