Date: Thu, 2 Jul 2015 15:40:32 -0400 From: RA H <rah.lists@gmail.com> To: RA H <rah.lists@gmail.com>, freebsd-scsi@freebsd.org Subject: Re: [iscsictl] connection to invalid target Message-ID: <CAFzyudi5oCCFok%2B9mQvo69mSB11iXNJSJm_iwPcH1SkZswQZZg@mail.gmail.com> In-Reply-To: <20150702083218.GA16246@brick.home> References: <CAFzyudhbMyEr9KEqo_%2Bxvr-AOnqinCJ%2B5Px9KZmTUpMsCWXPEQ@mail.gmail.com> <20150630194558.GA1223@brick.home> <CAFzyudjxb6k7E_BdCFAghCrF62RZ-93dNsfSifHGh2k9F3RmgA@mail.gmail.com> <20150702083218.GA16246@brick.home>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 2, 2015 at 4:32 AM, Edward Tomasz Napiera=C5=82a <trasz@freebsd= .org> wrote: > So basically it's not a FreeBSD bug? > Correct. > The problem here is that the discovery is performed by iscsid; the way > to implement it would be to make iscsictl add the discovery session, wait > for iscsid to finish discovery but not connect to the targets, report > targets, and then remove them. So basically pretty much what you are > doing anyway. > But that's not what I'm doing because I have no idea how to do discovery only through any means. Roughly, my process is as follows: * Get list of connected targets (iscsictl -L) * Do discovery+login (iscsictl -Ad <target ip>) * Get list of connected targets (iscsictl -L) * Filter newly connected targets * Compare newly connected target names to user-input target name and disconnect non-matching sessions If you could demonstrate how to implement the process you described above I'd be incredibly greatful. Also, apologies for not keeping this on the ML, I'm new at this...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFzyudi5oCCFok%2B9mQvo69mSB11iXNJSJm_iwPcH1SkZswQZZg>