On 01/28/2013 02:55 PM, torn5 wrote: > On 01/28/13 18:34, Mike Christie wrote: >> On 01/26/2013 08:45 AM, torn5 wrote: >>> Is there a way in open-iscsi to start and create devices in blocked mode >>> even if target is not available yet? (to be used together with long >>> recovery timeouts...) >> I think so - sort of. If you were to set >> node.session.initial_login_retry_max really high then that will instruct >> the initiator to retry the initial login process a lot of times. The >> idea would be that with enough retries it would still be retrying by the >> time the target came up. > > > Mike, thanks for your reply > > I actually need the blockdevice to be available (in blocked mode) just > after starting the initiator, even if the initiator wasn't able to > connect yet.
Ah ok. That might not be possible. We have to be able to establish a tcp/ip connection before the scsi layer and udev can setup a block device. We have to have that connection so the scsi layer can ask the target what devices exist. So if the target is not up to the point where it is accepting connections then there is nothing we can do. However, if you had already connected to the target, then brought the target down, the block devices will stay setup while the target is down. They will just queue IO or fail IO depending on your settings. Not sure if that helps. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. Visit this group at http://groups.google.com/group/open-iscsi?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
