On 10/19/2017 05:44 PM, Sagi Grimberg wrote:
Hi Sagi
With this patch, no such error log found on host side,
Awsome. that's the culprit...
but I found there is no nvme0n1 device node even get "nvme nvme0:
Successfully reconnected" on host.
That is expected because you did not persist a namespace UUID
which caused the kernel to generate a random one. That confused
the host as it got the same namespace ID with a different UUID.
Can you please set a uuid when you rerun the test?
I tried add uuid filed on rdma.json, it works well now.
[root@rdma-virt-00 ~]$ cat /etc/rdma.json
{
"hosts": [
{
"nqn": "hostnqn"
}
],
"ports": [
{
"addr": {
"adrfam": "ipv4",
"traddr": "172.31.0.90",
"treq": "not specified",
"trsvcid": "4420",
"trtype": "rdma"
},
"portid": 2,
"referrals": [],
"subsystems": [
"testnqn"
]
}
],
"subsystems": [
{
"allowed_hosts": [],
"attr": {
"allow_any_host": "1"
},
"namespaces": [
{
"device": {
"nguid": "ef90689c-6c46-d44c-89c1-4067801309a8",
"path": "/dev/nullb0",
"uuid": "00000000-0000-0000-0000-000000000001"
},
"enable": 1,
"nsid": 1
}
],
"nqn": "testnqn"
}
]
}
_______________________________________________
Linux-nvme mailing list
Linux-nvme@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/linux-nvme
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
