From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH 2/2] nvme/multipath: Fix multipath disabled naming collisions
Date: Mon, 29 Oct 2018 09:42:29 -0600 [thread overview]
Message-ID: <20181029154229.GA16586@localhost.localdomain> (raw)
In-Reply-To: <CAD4F464-15CC-44B9-9C72-B5F2BDFC5445@raithlin.com>
On Mon, Oct 29, 2018@03:37:46PM +0000, Stephen Bates wrote:
> Note how the /nvme/nvme0/ sysfs directory contains the nvme1n1
> namespace. Is this expected? I am not that familiar with the multipath
> code so I'm not sure if this is a bug or not but it sure is confusing.
> Disabling CONFIG_NVME_MULTIPATH reverts to the legacy naming
> convention. This happens in all the 4.19, 4.18 and 4.17 kernels we
> tested. I've not tried the for-next tree.
That is expected. We still need character devices to each controller path
for administration, but we don't need block devices to each namespace
path, so the numbers in the controller and block handles are independent
of each other.
next prev parent reply other threads:[~2018-10-29 15:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 21:49 [PATCH 0/2] nvme multipath naming fixes Keith Busch
2018-04-26 21:49 ` [PATCH 1/2] nvme/multipath: Disable runtime writable enabling parameter Keith Busch
2018-04-27 5:20 ` Christoph Hellwig
2018-04-27 15:48 ` Keith Busch
2018-10-30 18:17 ` Sagi Grimberg
2018-10-30 18:18 ` Sagi Grimberg
2018-10-30 18:24 ` Keith Busch
2018-10-31 5:28 ` Christoph Hellwig
2018-04-26 21:49 ` [PATCH 2/2] nvme/multipath: Fix multipath disabled naming collisions Keith Busch
2018-04-27 5:21 ` Christoph Hellwig
2018-10-29 15:37 ` Stephen Bates
2018-10-29 15:42 ` Keith Busch [this message]
2018-10-29 15:48 ` Stephen Bates
2018-10-29 15:55 ` Keith Busch
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=20181029154229.GA16586@localhost.localdomain \
--to=keith.busch@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