Bug 695435 - Implement more intelligent scsi_dh module attachment
Summary: Implement more intelligent scsi_dh module attachment
Keywords:
Status: CLOSED DUPLICATE of bug 690523
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Mike Christie
QA Contact: Storage QE
URL:
Whiteboard:
Depends On: 666304
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-11 18:12 UTC by Mike Christie
Modified: 2011-11-03 15:16 UTC (History)
25 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 666304
Environment:
Last Closed: 2011-11-03 15:16:17 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Comment 1 Mike Christie 2011-04-11 18:14:10 UTC 
This bz is for implementing more intelligent scsi_dh attachment. Today, it is based on which scsi_dh module is loaded first.

For Clarrions we want to do below. We will want to do something similar for other boxes that support vendor specific methods and ALUA.


In the standard inquiry return, byte 5 bits 4 and 5 (zero-relative) contain the
TPGS status. They'll be 00 on a PNR array and 11 on an ALUA box. The lun_state
information can be ambiguous as 0x01 and 0x02 are returned in both ALUA and PNR
modes but means different things;

0x01 (PNR)  LUN bound and assigned to the OTHER SP 
0x01 (ALUA) LUN bound and using the non-optimized path

0x02 (PNR)  LUN bound and assigned to THIS SP 
0x02 (ALUA) LUN bound and using the optimized path 

So I'd say we check TPGS first and then we can interpret the lun_state
accordingly based on that info...
Comment 2 RHEL Program Management 2011-05-13 15:26:07 UTC 
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has 
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed 
products. This request is not yet committed for inclusion in an Update release.
Comment 4 Mike Snitzer 2011-11-03 15:16:17 UTC 

*** This bug has been marked as a duplicate of bug 690523 ***
Note You need to log in before you can comment on or make changes to this bug.