From: Eric Curtin <ericcurtin17@gmail.com>
To: Jeffrey Lien <Jeff.Lien@wdc.com>
Cc: Keith Busch <kbusch@kernel.org>,
Alex Gronseth <Alex.Gronseth@wdc.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: NVMe CLI Commit - Input expects device name without /dev
Date: Wed, 10 Feb 2021 18:35:56 +0000 [thread overview]
Message-ID: <CANpvso5nv0LO6XwAVtj8Lc=4HbxUjjNnTmj9T7ap5F=3mccKoA@mail.gmail.com> (raw)
In-Reply-To: <BYAPR04MB5656896D86A830305A2AFE31EA8D9@BYAPR04MB5656.namprd04.prod.outlook.com>
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@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
>
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2021-02-10 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 18:21 NVMe CLI Commit - Input expects device name without /dev Jeffrey Lien
2021-02-10 18:35 ` Eric Curtin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANpvso5nv0LO6XwAVtj8Lc=4HbxUjjNnTmj9T7ap5F=3mccKoA@mail.gmail.com' \
--to=ericcurtin17@gmail.com \
--cc=Alex.Gronseth@wdc.com \
--cc=Jeff.Lien@wdc.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.