On Aug 20, 3:30pm, Andrew Vasquez wrote:
} Subject: Re: Poisoning of Linux initiators on SCST reboot.
Hi Andrew, thanks for the note.
> > There is a remote port defined for the target server. The port WWN
> > and FCID match previous values. The only difference is the LUN on
> > which the storage is being delivered.
> >
> > We tore down the SCST storage definition on the target and re-mapped
> > the storage as LUN 1 but this had no affect on the situation. That
> > isn't really surprising since the problem appears be secondary to the
> > initiator and target being unable to establish an N_PORT relationship.
> >
> > I would be interested in any thoughts the group might have. From the
> > perspective of the initiators the behavior seems somewhat identical to
> > what we experienced earlier. The Qlogic driver is essentially
> > 'poisoned' with respect to its ability to access the remote port which
> > has seen a change in configuration.
> These upstream changes are in the queue of updates to be pushed for
> RHEL5.3.
Very good to hear, the client guys will be glad to hear that.
In the meantime is our analysis correct that this is the same problem,
only caused by the LUN change rather than the role changes? Knowing
that would be very helpful.
If so we are hosed and will need to proceed with our outage to recover
the initiators. It will also impact the next round of migrations we
need to do.
> Regards,
> Andrew Vasquez
Thanks for the information, will look forward to confirmation on the above.
Have a good evening.
}-- End of excerpt from Andrew Vasquez
As always,
Dr. G.W. Wettstein, Ph.D. Enjellic Systems Development, LLC.
4206 N. 19th Ave. Specializing in information infra-structure
Fargo, ND 58102 development.
PH: 701-281-1686
FAX: 701-281-3949 EMAIL: greg@xxxxxxxxxxxx
------------------------------------------------------------------------------
"How appropriate, you fight like a cow."
-- Guybrush Threepwood
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
