Date: Tue, 3 Mar 2015 19:23:23 +0100 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= <trasz@FreeBSD.org> To: Aafak Mohammad <aafak.mohammad@cloudbyte.com> Cc: freebsd-scsi@freebsd.org Subject: Re: iSCSI initiator: iscontrol cannot be stopped or killed Message-ID: <20150303182323.GA5941@brick.home> In-Reply-To: <CAC5dOi=C_R0nwi4qT56_Nw8=%2B_0Xc348LR4QteeD-1t8VbgFSw@mail.gmail.com> References: <CAC5dOi=bf-x2_UzWUexwKPmKA7_EVngFUD_ZWy9RNji9nfW9xw@mail.gmail.com> <20150303084606.GA4495@brick.home> <CAC5dOi=C_R0nwi4qT56_Nw8=%2B_0Xc348LR4QteeD-1t8VbgFSw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I believe the iXsystems has their fork based on 9 with iSCSI backport, but I'm not sure if it includes the client. Their source tree can be found here: https://github.com/trueos/trueos. On 0303T1508, Aafak Mohammad wrote: > Thanks for helping. > But for now i cannot upgrade it. > Can i get only iscsictl for 9.2? > i mean get it from 10.1 and use only this feature in 9.2 > will it work ? > > On Tue, Mar 3, 2015 at 2:16 PM, Edward Tomasz Napierała <trasz@freebsd.org> > wrote: > > > On 0303T1445, Aafak Mohammad wrote: > > > Problem: the iscontrol process starts normally and establishes > > > a session and brings up a device, but it cannot be stopped. > > > It does not react to a HUP signal, and neither to KILL. > > > > > > The /dev/da0 device is operational and the remote disk remains > > > normally accessible, regardless of how I try to (unsuccessfully) > > > shutdown the iscontrol process. The ps reports the state of the > > > process as "Ds", not doing anything. A ktrace does not show any > > > reaction to a received signal. A restart seems to be necessary > > > to break the iSCSI session. > > > > Well, that's one of the reasons it's obsolete. Could you try > > to upgrade to 10.1 and try the new iSCSI initiator, iscsictl/iscsid?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150303182323.GA5941>