Bug 1919277 - RFE - Request to grab /etc/dasd.conf by default
Summary: RFE - Request to grab /etc/dasd.conf by default
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: sos
Version: 8.2
Hardware: s390
OS: Linux
Target Milestone: rc
: 8.0
Assignee: Pavel Moravec
QA Contact: Miroslav Hradílek
Depends On:
TreeView+ depends on / blocked
Reported: 2021-01-22 14:02 UTC by John Pittman
Modified: 2021-11-10 07:39 UTC (History)
11 users (show)

Fixed In Version: sos-4.1-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-11-09 19:36:07 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github sosreport sos pull 2381 0 None closed [s390] Collect dasd.conf file 2021-02-09 05:33:11 UTC
Red Hat Product Errata RHEA-2021:4388 0 None None None 2021-11-09 19:36:22 UTC

Description John Pittman 2021-01-22 14:02:11 UTC
Description of problem:

Request to grab /etc/dasd.conf by default

Version-Release number of selected component (if applicable):


Additional info:

The /etc/dasd.conf is the common configuration file for the dasd portion of s390, similar to how /etc/multipath.conf is to multipath.  It has settings like failover timings, readonly settings, diag settings, etc.  It's very useful to see what the customer has set in this file when doing an initial analysis of s390 and more specifically dasd (s390 storage) issues.  It's also useful to have when suggesting dasd tuning changes to the customer.

Comment 1 Jose Castillo 2021-01-22 15:08:09 UTC
Thank you for the report John. I've created a pull request upstream because I couldn't find an existing one:


Lets see if the sos team has any feedback about it.

Comment 17 errata-xmlrpc 2021-11-09 19:36:07 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 (sos 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.


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