Re: iSCSI: handling of persistent reserves during initiator reboot

[Sandeep Joshi <sandeepj@research.bell-labs.com>]

Jim Hafner wrote:
> 
> Tom,
> 
> Here's my two cents. Apologies for being long-winded.  In short, I think I
> agree with most of your sentiment.
> 
> 1) In order to accommodate Persistent Reservations (and a few other SCSI
> things), I think it is important to have some mechanism for an initiator to
> reestablish some nexus state information through logout/login.  The current
> thinking in N&DT is that the initiator should reuse it's old ISID and the
> target should respond with the old TSID (thereby rebuilding the nexus).
> Note, the initiator starts with TSID=0, as if it was a new session.  The
> target that remembers the old ISID/TSID pair (can reuse the old TSID). Keep
> in mind that that target is already remembering some state information (the
> reservation) about the ISID/TSID (and Names) relationship in the nexus, so
> this isn't a big deal.

If I am not mistaken, isnt this also adding to initiator state ?
Initiators now have to remember the ISIDs used with every target 
(or have only one!)

And doesnt this also add state to iSCSI-FC bridges...?

Regards,
-Sandeep