From owner-freebsd-scsi@FreeBSD.ORG Mon Mar 30 20:49:11 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 B497F36B for ; Mon, 30 Mar 2015 20:49:11 +0000 (UTC) Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) (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 42F722F9 for ; Mon, 30 Mar 2015 20:49:11 +0000 (UTC) Received: by wgbdm7 with SMTP id dm7so82235720wgb.1 for ; Mon, 30 Mar 2015 13:49:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=axekvbnnWdrkmwVvlzML+nYwMmUWH9V58kV05cmlkV0=; b=uCZVR/60KuwUDeug3mHB9qH/PFYkJ/0E5RL+oJqS9SHtTslR+lG5eib3CmrC/ASjAF +Krr5jJOL3eevksjYFlIOpnHxPqFVnb4qm5oEETO1FPi9FYR8yKoUl4pjLJg1PwOXscB kFNrsa7E3NLFCX3XcIT6J0qr5bWuRFWoknt7DHANnp+IrUahiSUFdrC53lrDghk9q8h4 b8/tYTySCyQTjcGBvDrs+ZsftR+YpqDA5ArGS5Q55BwBJv/WCl5NHYFiPQsDUFYj5t4x WRUEeiM0PmySB2k9dmlIrDt26RsHwQuFrRkU0ZpraizKW35tWhpCmPwDe4tXBy6Nryda QmOA== X-Received: by 10.180.75.243 with SMTP id f19mr25872601wiw.94.1427748549240; Mon, 30 Mar 2015 13:49:09 -0700 (PDT) Received: from brick.home (abvb139.neoplus.adsl.tpnet.pl. [83.8.199.139]) by mx.google.com with ESMTPSA id ei8sm17912122wib.10.2015.03.30.13.49.07 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Mar 2015 13:49:07 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Date: Mon, 30 Mar 2015 22:49:05 +0200 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= To: Aafak Mohammad Subject: Re: Cannot connect iSCSI targets created on Nexent box Message-ID: <20150330204905.GA12290@brick.home> Mail-Followup-To: Aafak Mohammad , freebsd-scsi@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-scsi@freebsd.org 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: Mon, 30 Mar 2015 20:49:11 -0000 On 0330T1716, Aafak Mohammad wrote: > Hi > I am using freebsd 9.2 and back ported iscsictl/iscsid and native kenel > iscsi changes from 10.1 to 9.2 > I am able to discover and connect iSCSI targets on my Ubuntu box from > freebsd 9.2 and able to create zpool on those iscsi targets > > Now i want to use nexenta targets LUNs for zpool creation > so as i tried to connect it got the system into following state: > > root@trunk-mar26:~ # iscsictl > Target name Target addr State > iqn.2012-05.local.mynet:storage.sys1 10.11.1.136 Connected: da8 da9 > da10 > iqn.2012-05.local.mynet:storage.sys2 10.11.1.136 Connected: da11 da12 > da13 > > *iqn.1986-03.com.sun:02:7957828f-1551-e04c-ed10-cce469c63bfa > 20.10.20.7 Connected: probe0 > iqn.1986-03.com.sun:02:b3031b28-29d1-40d5-9f02-a95a428d096e > 20.10.20.7 Connected: probe1 * > > As you can see first two iSCSI target(on Ubuntu) connected successfully and > same device nodes i can see on camcontrol devlist > but the last two saying connected but device nodes probe0, probe1 are not > in camcontrol devlist > > */var/log/messages:* > > Mar 30 17:05:52 trunk-mar26 iscsid[28641]: 20.10.20.7 > (iqn.1986-03.com.sun:02:b3031b28-29d1-40d5-9f02-a95a428d096e): Capsicum > capability mode not supported > Mar 30 17:05:52 trunk-mar26 iscsid[28640]: 20.10.20.7 > *(iqn.1986-03.com.sun:02:7957828f-1551-e04c-ed10-cce469c63bfa): received > final login response without the "T" flagMar 30 17:05:52 trunk-mar26 > iscsid[28641]: 20.10.20.7 > (iqn.1986-03.com.sun:02:b3031b28-29d1-40d5-9f02-a95a428d096e): received > final login response without the "T" flag* I think this is fixed by r271706. Can you update the code from 10.1-RELEASE to 10-STABLE and see if it works? Thanks!