Re: [SPDK] NVMe-oF question with SPDK

Re: [SPDK] NVMe-oF question with SPDK

[Liu, Changpeng]

[-- Attachment #1: Type: text/plain, Size: 2239 bytes --]

SPDK already provides such framework right now, but NVMeoF part is still missing, 
the configuration can be saved to JSON file(Already done) and can be loaded for next start(missing).


> -----Original Message-----
> From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Shi Bingxun
> Sent: Thursday, September 20, 2018 3:21 PM
> To: spdk(a)lists.01.org
> Cc: shibx(a)lenovo.com
> Subject: [SPDK] NVMe-oF question with SPDK
> 
> Dear experts,
> 
> 
> Could you help to advice for my issues with SPDK? I'm trying to setup NVMe over
> fabric environment using SPDK. With below listed steps, I can successfully
> connect NVMe subsystem on initiator. So I think my steps should work.  But  I
> found once the target reboots,  the setup information on the target will be gone,
> like the created NVMe bdevs, I'm really confused. Won't the created bdev be
> saved?
> 
> ----------------------------------------------------------------------------------------------
> 
> On NVMe target:
> 
> sudo scripts/setup.sh
> ./app/nvmf_tgt/nvmf_tgt &
> cd scripts
> ./rpc.py construct_nvme_bdev -b NVMe1 -t PCIe -a 0000:03:00.0
> ./rpc.py construct_nvmf_subsystem nqn.2016-06.io.spdk:cnode1 "trtype:RDMA
> traddr:192.168.1.2 trsvcid:4420" "" -a -s SPDK00000000000001 -n NVMe1n1
> 
> On initiator:
> nvme connect -t rdma -n "nqn.2016-06.io.spdk:cnode1" -a 192.168.1.2 -s 4420
> ------------------------------------------------------------------------------------------------
> When target reboots, I run below command to check the bdev, it reports
> "*ERROR*: bdev 'Nvme0n1' does not exist"
> ./app/nvmf_tgt/nvmf_tgt &
> ./rpc.py get_bdevs -b NVMe1n1
> 
> 
> On SPDK website, there is a configuration file followed nvmf_tgt command. I tried
> to add "TransportID "trtype:PCIe traddr:0000:03:00.0" NVMe1" in the
> configuration file, NVMe1n1 bdev is available after this command. But looks like
> the NVMe bdev is created again when the command runs, is my understanding
> correct?
> 
> app/nvmf_tgt/nvmf_tgt -c /path/to/nvmf.conf
> 
> 
> 
> Thanks
> Neil
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk

[SPDK] NVMe-oF question with SPDK

[Shi Bingxun]

[-- Attachment #1: Type: text/plain, Size: 1558 bytes --]

Dear experts,


Could you help to advice for my issues with SPDK? I'm trying to setup NVMe over fabric environment using SPDK. With below listed steps, I can successfully connect NVMe subsystem on initiator. So I think my steps should work.  But  I found once the target reboots,  the setup information on the target will be gone, like the created NVMe bdevs, I'm really confused. Won't the created bdev be saved?

----------------------------------------------------------------------------------------------

On NVMe target:

sudo scripts/setup.sh
./app/nvmf_tgt/nvmf_tgt &
cd scripts
./rpc.py construct_nvme_bdev -b NVMe1 -t PCIe -a 0000:03:00.0
./rpc.py construct_nvmf_subsystem nqn.2016-06.io.spdk:cnode1 "trtype:RDMA traddr:192.168.1.2 trsvcid:4420" "" -a -s SPDK00000000000001 -n NVMe1n1

On initiator:
nvme connect -t rdma -n "nqn.2016-06.io.spdk:cnode1" -a 192.168.1.2 -s 4420
------------------------------------------------------------------------------------------------
When target reboots, I run below command to check the bdev, it reports "*ERROR*: bdev 'Nvme0n1' does not exist"
./app/nvmf_tgt/nvmf_tgt &
./rpc.py get_bdevs -b NVMe1n1


On SPDK website, there is a configuration file followed nvmf_tgt command. I tried to add "TransportID "trtype:PCIe traddr:0000:03:00.0" NVMe1" in the configuration file, NVMe1n1 bdev is available after this command. But looks like the NVMe bdev is created again when the command runs, is my understanding correct?

app/nvmf_tgt/nvmf_tgt -c /path/to/nvmf.conf



Thanks
Neil