From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.0.4-1.3.1 Firefox/1.0.4 Description of problem: the current RHEL kernel contains an old version of the fc transport class. The newer one (in kernel 2.6.13-rc3) has a host attribute called port_id which gives the WWN of the HBA. This WWN is necessary to get fencing via reservations to work with dm-multipath in a cluster. The request is that at least the port_id be added to the fc host attributes in the next feasible RHEL kernel (although a full backport of the current fc transport class would be nice since it's the one that supports the vanilla kernel emulex driver) Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: try to fence a cluster running dm-multipath with reservations Additional info:
I do not think we are going to be able to upgrade to the upstream class because the LLD maintainers are happy where they are, we have some KABI issues, and the dm-multipath devs will not be happy.
Created attachment 119447 [details] add host port_id We could try this patch. It backports the the shost port_id (lpfc actually has this value on the scsi_host attrs today) and adds support for lpfc and qla2xxx. The KABI police may have problems with it becuase of the fc_function_template additions and we may have to fall back to just adding the port_id to qlogics scsi host attrs. If this is ok with you jejb then I will send it off internally to see if it passes the review.
Created attachment 119448 [details] add host port_id We could try this patch. It backports the the shost port_id (lpfc actually has this value on the scsi_host attrs today) and adds support for lpfc and qla2xxx. The KABI police may have problems with it becuase of the fc_function_template additions and we may have to fall back to just adding the port_id to qlogics scsi host attrs. If this patch is ok with jejb then I will send it off internally to see if it passes the review.
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 the 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. http://rhn.redhat.com/errata/RHSA-2006-0132.html