[Bug Report] nvme-cli commands fails to open head disk node and print error

[Kamaljit Singh]

Hi Daniel,
Your question about the nvme-cli version makes me wonder if there is a version compatibility matrix (nvme-cli vs kernel) somewhere you could point me to? I didn't see such info in the nvme-cli release notes.

For example, I've seen issues with newer than nvme-cli v1.16 on Ubuntu 22.04 (stock & newer kernels). From a compatibility perspective I do wonder whether circumventing a distro's package manager and directly installing newer nvme-cli versions might be a bad idea. This could possibly become dire if there were intentional version dependencies across the stack.
 
Thanks,
Kamaljit
 

From: Linux-nvme <linux-nvme-bounces at lists.infradead.org> on behalf of Daniel Wagner <dwagner at suse.de>
Date: Thursday, March 28, 2024 at 01:46
To: Nilay Shroff <nilay at linux.ibm.com>
Cc: Christoph Hellwig <hch at lst.de>, Keith Busch <kbusch at kernel.org>, linux-nvme at lists.infradead.org <linux-nvme at lists.infradead.org>, linux-block at vger.kernel.org <linux-block at vger.kernel.org>, axboe at fb.com <axboe at fb.com>, Gregory Joyce <gjoyce at ibm.com>
Subject: Re: [Bug Report] nvme-cli commands fails to open head disk node and print error
CAUTION: This email originated from outside of Western Digital. Do not click on links or open attachments unless you recognize the sender and know that the content is safe.


On Thu, Mar 28, 2024 at 12:00:07PM +0530, Nilay Shroff wrote:
> From the above output it's evident that nvme-cli attempts to open the disk node /dev/nvme0n3
> however that entry doesn't exist. Apparently, on 6.9-rc1 kernel though head disk node /dev/nvme0n3
> doesn't exit, the relevant entries /sys/block/nvme0c0n3 and /sys/block/nvme0n3 are present.

I assume you are using not latest version of nvme-cli/libnvme. The
latest version does not try to open any block devices when scanning the
sysfs topology.

What does `nvme version` say?