Bug 444839 - FC device state information is omitted
Summary: FC device state information is omitted
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: sos
Version: 5.4
Hardware: noarch
OS: Linux
Target Milestone: rc
: ---
Assignee: Adam Stokes
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2008-05-01 00:30 UTC by Marco Grigull
Modified: 2012-04-23 12:24 UTC (History)
3 users (show)

Clone Of:
Last Closed: 2009-09-02 07:29:56 UTC

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2009:1418 normal SHIPPED_LIVE sos bug fix and enhancement update 2009-09-02 07:29:42 UTC

Description Marco Grigull 2008-05-01 00:30:37 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20080409 Red Hat/ Firefox/

Description of problem:
q2xxx and lpfc device state information used to be presented by the kernel under /proc/scsi/ and is now exclusivly provided via /sys/

The sosreport captures the required /proc/scsi heirarchy needed by GSS Production support for ascertaining SAN connectivity iusses.  As the information is now presented in a way that the sosreport does not capture, this information has to be specified manually.

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

How reproducible:

Steps to Reproduce:
1. run sosreport on system with QLA adaptors
2. open the report
3. wonder what state the adaptor is in.

Actual Results:

Expected Results:
directory tree under /sys/state/

Additional info:

lpfc and qla2xxx are affected, possibly more now or in the future

Comment 10 errata-xmlrpc 2009-09-02 07:29:56 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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