From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: multipart/mixed; boundary="===============7941857225690976814=="
MIME-Version: 1.0
From: Harris, James R <james.r.harris at intel.com>
Subject: Re: [SPDK] Need help for iSCSI configuration for NVMe disc
Date: Wed, 24 May 2017 16:20:03 +0000
Message-ID: <520CA476-8C35-4FBB-B345-AF3371CFF243@intel.com>
In-Reply-To: E3BE516C-3D1C-4600-8133-CA0CEA77D082@cloudsimple.com
List-ID: <spdk@lists.01.org>
To: spdk@lists.01.org

--===============7941857225690976814==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable


> On May 24, 2017, at 4:10 AM, Kiran Dikshit <kdikshit(a)cloudsimple.com> w=
rote:
> =

> Hi All,
> =

> I am trying to configure iSCSI for a NVMe drive and getting the below err=
or=E2=80=99s. I have unbound the NVMe drive from kernel using the setup.sh.
> =

> tgt_node.c: 718:spdk_iscsi_tgt_node_construct: ***ERROR*** Could not cons=
truct SCSI device
> tgt_node.c: 984:spdk_cf_add_iscsi_tgt_node: ***ERROR*** tgt_node1: add_is=
csi_target_node error
> tgt_node.c:1010:spdk_iscsi_init_tgt_nodes: ***ERROR*** spdk_cf_add_iscsi_=
tgt_node() failed
> iscsi_subsystem.c: 965:spdk_iscsi_subsystem_init: ***ERROR*** spdk_iscsi_=
init_tgt_nodes() failed
> app.c: 404:spdk_app_init: ***ERROR*** spdk_subsystem_init() failed
> =

> =

> =

> Below is the section of my iscsi.conf.in file for reference.
> =

> # NVMe configuration options
> [Nvme]
> # NVMe Device Whitelist
> # Users may specify which NVMe devices to claim by their PCI
> # domain, bus, device, and function. The format is dddd:bb:dd.f, which is
> # the same format displayed by lspci or in /sys/bus/pci/devices. The seco=
nd
> # argument is a "name" for the device that can be anything. The name
> # is referenced later in the Subsystem section.
> #
> # Alternatively, the user can specify ClaimAllDevices. All
> # NVMe devices will be claimed and named Nvme0, Nvme1, etc.
> # BDF 0000:00:00.0 Nvme0
>   BDF 0000:0a:00.0 Nvme3

Hi Kiran,

The format of the NVMe section changed in the last SPDK release, so that we=
 could add support for remote NVMe-oF devices as well.

Can you try the following instead?

[Nvme]
  TransportID =E2=80=9Ctrtype:PCIe traddr:0000.0a:00.0=E2=80=9D Nvme3

The comment for spdk_nvme_transport_id_parse() in include/spdk/nvme.h descr=
ibes the format in more detail, including how to specify NVMe-oF targets.

Thanks,

-Jim

> =

> [TargetNode1]
>   TargetName disk2
>   TargetAlias "Data Disk2"
>   Mapping PortalGroup1 InitiatorGroup1
>   AuthMethod Auto
>   AuthGroup AuthGroup1
>   UseDigest Auto
>   LUN0 Nvme3
>   QueueDepth 64
> =

> =

> Thank you
> Kiran
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk


--===============7941857225690976814==--