Score:0

Figure out what NVME target device initiator is using

be flag

I've got a simple NVME-TCP stack going (Linux to Linux machines), and it works fine.

One one machine I've got the initiator going and it presents block device in typical form (e.g. /dev/nvme2n1). Target is exposing one of its nvme devices as through NVME-TCP.

The question I have is as follows: either programmatically or from the command line, from either the target or initiator side, can I identify the device mapping from initiator to target?

For example, I would like to be able to know that /dev/nvme2n1 on the initiator side is /dev/nvme5n1 (or whatever) on the target side. And I'd like to be able to do that from the initiator preferably, but either initiator or target side will work in a pinch.

Is this possible? If so, how?

Thanks!

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.