From owner-freebsd-scsi@FreeBSD.ORG Tue Mar 3 10:08:27 2015 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B6CE6F78 for ; Tue, 3 Mar 2015 10:08:27 +0000 (UTC) Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 30C9E100 for ; Tue, 3 Mar 2015 10:08:26 +0000 (UTC) Received: by wiwl15 with SMTP id l15so21374020wiw.3 for ; Tue, 03 Mar 2015 02:08:18 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=OCgViXaHXx9lg1BUwKa8bQ1zWVXmuyUUlSapsru4T1g=; b=TDHcScXeZT7T3SBd/SIz8OUI/2Ej4moEX1Ymw4thRt36xpyp9w425WQ9/OBK7TcDdF 7PyH7nb6VmedcqdC5J410k+IqSO9D4NrdVLcGiVL1Kn5/ycMn+1azGp3sp+aAEPx+j+a seqYaDk9EMFKEcgNwcEcAkUz7kIcSvSiWdhOjDeCKWIbiav7ppkWfaCliF7Z8XBRWoGM z8VF5yiBo3z9XRi5f4DxM/I1Ye4DDTsEeXCEYlhgcPequfM2U58UMW1AKb6uS1XLpGqo KyujiCU0swLbT+DaQ6ryWiRpuZsvoA4MBlLej3omS/RQfCRl60GibXeOLCgnbhCKojKO 7Jmg== X-Gm-Message-State: ALoCoQl+Ly3X7+dAapNbdQ0nzO2plqNJU2tHy8ITmJGZ2Bx+1c18eyW85ZP9B/HbdGin7Ybe/em4 MIME-Version: 1.0 X-Received: by 10.180.149.206 with SMTP id uc14mr44014252wib.57.1425375495666; Tue, 03 Mar 2015 01:38:15 -0800 (PST) Received: by 10.194.37.97 with HTTP; Tue, 3 Mar 2015 01:38:15 -0800 (PST) In-Reply-To: <20150303084606.GA4495@brick.home> References: <20150303084606.GA4495@brick.home> Date: Tue, 3 Mar 2015 15:08:15 +0530 Message-ID: Subject: Re: iSCSI initiator: iscontrol cannot be stopped or killed From: Aafak Mohammad To: Aafak Mohammad , freebsd-scsi@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Mar 2015 10:08:27 -0000 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=C5=82a 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? > > --=20 Thanks and Regards, Aafak [image: cid:image001.png@01CF7E5A.8A69F530] Plot No. : 2799 & 2800, Srinidhi Bldg, 3rd Floor, 27th Main, Sector =E2=80=93 1, HSR Layout, Bangalore =E2=80=93 560102, Call: (91)-80-2258-2804 www.cloudbyte.com