NVMe CLI Commit - Input expects device name without /dev

Eric Curtin ericcurtin17 at gmail.com
Wed Feb 10 13:35:56 EST 2021


Sorry yes, it made sense to print this error for this case:

https://github.com/linux-nvme/nvme-cli/issues/879

But not for others, I'll remove that fprintf line. Here's the fix:

https://github.com/linux-nvme/nvme-cli/pull/905

Apologies for any inconvenience caused.


On Wed, 10 Feb 2021 at 18:21, Jeffrey Lien <Jeff.Lien at wdc.com> wrote:
>
> Eric,
> The subject commit (ID dcfe0156360deaefa26b1d00053a791eefe397d1) is causing the following errors with the Linux 5.9 kernel:
> Failed to open /sys/class/nvme-subsystem/nvme-subsys0/nvme0/hostnqn: No such file or directory
> Failed to open /sys/class/nvme-subsystem/nvme-subsys0/nvme0/hostid: No such file or directory
> Failed to open /sys/class/nvme-subsystem/nvme-subsys1/nvme1/hostnqn: No such file or directory
> Failed to open /sys/class/nvme-subsystem/nvme-subsys1/nvme1/hostid: No such file or directory
> Failed to open /sys/class/nvme-subsystem/nvme-subsys2/nvme2/hostnqn: No such file or directory
> Failed to open /sys/class/nvme-subsystem/nvme-subsys2/nvme2/hostid: No such file or directory
>
> I'm seeing them on the  format and nvme list command.  They don't seem to impact function but do generate questions.  Do know of a way to resolve?
>
> Thanks
>
> Jeff Lien
>



More information about the Linux-nvme mailing list