+++ This bug was initially created as a clone of Bug #578005 +++
MTU change (or other network reset events) with active iSCSI sessions will fail. iSCSI sessions do not recover and resources are leaked.
This upstream patch will fix it:
Requesting this to be included in RHEL5.5.z.
2 more cnic patches are required to completely fix the MTU change issue:
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
You can download this test kernel from http://people.redhat.com/jwilson/el5
Detailed testing feedback is always welcomed.
With kernel-2.6.18-221.el5 and iscsi-initiator-utils-188.8.131.522-10 (uIP 0.5.15), iSCSI sessions still do not recover after changing MTU sizes. The problem appears to be uIP-related since it does work when I add a newer internal version of uIP on top of the above components.
Slight mistake to the above iscsi-initiator version... it should be iscsi-initiator-utils-184.108.40.2062-2.el5.x86_64.rpm (the latest RH5.6 initiator at the moment... http://people.redhat.com/mchristi/iscsi/rhel5.6/iscsi-initiator-utils/).
With kernel-2.6.18-221.el5 and iscsi-initiator-utils-220.127.116.112-2 (uIP
0.5.15), iSCSI sessions still do not recover after changing MTU sizes. The
problem appears to be uIP-related since it does work when I add a newer
internal version of uIP on top of the above components.
What is still needed? Is iscsi-initiator-utils's uip missing a patch from another bugzilla?
This problem is no longer seen with kernel-2.6.18-232.el5 and iscsi-initiator-utils-18.104.22.1682-6.el5.x86_64.rpm (uIP 0.6.2.2).
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.