From: keith.busch@linux.intel.com (Keith Busch)
Subject: Devices expected?
Date: Fri, 7 Sep 2018 09:55:25 -0600 [thread overview]
Message-ID: <20180907155524.GA857@localhost.localdomain> (raw)
In-Reply-To: <DE927C68B458BE418D582EC97927A9288003FD37@ORSMSX113.amr.corp.intel.com>
On Fri, Sep 07, 2018@03:40:45PM +0000, Gruher, Joseph R wrote:
> > > In general, my question is whether this is expected behavior? If a
> > > bug, is it fixed in a newer kernel? We are trying to track some disk
> > > stats and the unexpected (at least from our perspective) behavior in
> > > /proc/diskstats is causing us some confusion. Thanks!
> >
> > With the exception of the 'lsblk' error message, I think all your results are
> > expected when CONFIG_NVME_MUTLIPATH=y.
>
> Thanks Keith. I just pulled the Ubuntu mainline kernel package, rather than building my own, so I guess they have NVMeoF multipathing on by default.
If you do not want to use this feature, you may disable it with kernel
parameter "nvme_core.multipath=0" if modifying the kernel or its config
is not desirable.
> Does nvme2c1n1 represent one path for the nvme2n1 device to use? If I connected a second path I would see something like nvme2c2n1 pop up as well?
Yes, that is what that those names represent.
In your example, the '2' in nvme2 is the subsystem instance, which
is just a unique number software assigned to the subsystem. The '1'
in nvme2c1 is the controller id that identify controller reports, so it
may not necessarily start at 1 or increase sequentially.
next prev parent reply other threads:[~2018-09-07 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 20:26 Devices expected? Gruher, Joseph R
2018-09-06 21:05 ` Keith Busch
2018-09-07 15:40 ` Gruher, Joseph R
2018-09-07 15:55 ` Keith Busch [this message]
2018-09-11 7:23 ` Christoph Hellwig
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=20180907155524.GA857@localhost.localdomain \
--to=keith.busch@linux.intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).