Red Hat Bugzilla – Bug 111904
zfcp: error recovery stall in case of unavailable nameserver
Last modified: 2007-11-30 17:06:59 EST
Description of problem:
symptom: modprobe hangs if nameserver port is inaccessible
problem: error recovery is infinitely waiting for the completion of
the "nameserver open" action which was not issued at all because the
nameserver port was already known to be inaccessible and thus had
been marked as failed
solution: fail "open port" action immediately if issueing on "open
nameserver port" action is not possible though required
based on discussions with Martin Peschke, I lowered the priority
Ingolf, please add LTC number. I am unable to identify this problem
by reading descriptions on DeveloperWorks.
LTC number is 3615
Ingolf - does Pete have access to that number and the issue behind it ?
If not please post a copy here, thanks.
Bob, I do not have access, but LTC numbers are used by DeveloperWorks,
so it is sufficient to identify patches from that source.
It would be nice if Ingolf attached them, but hey... whatever works.
I'll integrate and post today or on Monday, depending how well
if it helps, I can add the LTC bugzillas to the Red Hat bugzillas.
That would be easier, instead of adding the whole patch to RH
bugzilla. By the way Bob should have a table that give the
Bob for your information: with the LTC bugzillas or the RH bugzilla
summary you can easily identify our patches at developer works.
This problem is part of August code drop at
-2.4.21-s390-04-june2003.shtml. If you follow that link, you will
find a short problem description and a tar file, that holds the per-
This is strange. I am sure I folded LTC 3615 into the bug 104460,
so this should be resolved in GA (even before U1 !). It was a
part of "the 38". I'll investigate further in a moment.
There's no doubt that LTC 3615 is fixed long ago.
I am marking this modified in 2.4.21-9.EL.
Ingolf, please confirm and close.
Bug was fixed with zfcp version 220.127.116.11, while 2.4.21-9.EL uses zfcp
version 18.104.22.168. Apart from that version number, this RHEL kernel
actually carries along the modification comprising the fix. Please close.
This was fixed in RHEL3 U1.