On Dec 5, 2012, at 8:12 PM, Mike Christie <micha...@cs.wisc.edu> wrote:
> On 12/04/2012 06:58 PM, Lee Duncan wrote: >> On Dec 4, 2012, at 4:51 PM, Mike Christie <micha...@cs.wisc.edu> wrote: >> >>> On 12/04/2012 05:22 PM, Lee Duncan wrote: >>>> Hi Mike: >>>> >>>> I am trying to create a Persistent Reservations test suite for iSCSI >>>> targets, and i was wondering if I could use open-iscsi on the initiator >>>> side to do that. >>>> >>>> Part of the requirement is that I need to support multiple I_T Nexuses, >>>> since Group Reservations are based on the I_T Nexus. If I can send from >>>> multiple initiators on the same host, I could eliminate the current >>>> requirement to test from multiple hosts. >>>> >>> >>> You can create multiple initiators. Just create ifaces with different >>> initiator names. The problem though is that the iSID is not persistent >>> across logins, so if you were to login/logout using iscsiadm from the >>> target for any reason then the persistent reservations are going to get >>> messed up. >>> >> >> Would that be a problem for Persisting a reservation in general, then? > > Not sure what you mean exactly. If you are using the reservation for > just the life of the session then no, but I do not think that is common. > It seems like you are likely to reboot your box or login/logout of the > target once in a while. > > The idea with Persistent Reservations is that they should persist across target power outages. But if the iSID changes with a new connection, then when the target comes back it might not recognize the reservation holder because there will be a new connection. All speculation, of course, without looking at the code ... -- Lee Duncan -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
