From: Christoph Hellwig <hch@lst.de>
To: Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
Sagi Grimberg <sagi@grimberg.me>, Jens Axboe <axboe@fb.com>,
Christoph Hellwig <hch@lst.de>,
Potnuri Bharat Teja <bharat@chelsio.com>,
Keith Busch <keith.busch@intel.com>,
Hannes Reinecke <hare@suse.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH v2] nvme: create 'paths' entries for hidden controllers
Date: Thu, 8 Nov 2018 10:16:28 +0100 [thread overview]
Message-ID: <20181108091628.GA4217@lst.de> (raw)
In-Reply-To: <20181101232955.19329-1-cascardo@canonical.com>
On Thu, Nov 01, 2018 at 08:29:55PM -0300, Thadeu Lima de Souza Cascardo wrote:
> When using initramfs-tools with only the necessary dependencies to mount
> the root filesystem, it will fail to include nvme drivers for a root on a
> multipath nvme. That happens because the slaves relationship is not
> present.
>
> As discussed in [1], using slaves will break lsblk, because the slaves are
> hidden from userspace, that is, they have no real block device, just an
> entry under sysfs.
I wonder if the better way would be to unhide the slaves, but always
have a claim on them, so that others can't really use them? While the
hiding idea seamed very neat it seems to cause a fair amount of problems
after all.
prev parent reply other threads:[~2018-11-08 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 23:29 [PATCH v2] nvme: create 'paths' entries for hidden controllers Thadeu Lima de Souza Cascardo
2018-11-08 9:16 ` Christoph Hellwig [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=20181108091628.GA4217@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=bharat@chelsio.com \
--cc=cascardo@canonical.com \
--cc=hare@suse.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=martin.petersen@oracle.com \
--cc=sagi@grimberg.me \
/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