[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181005073245.GA24224@lst.de>
Date: Fri, 5 Oct 2018 09:32:45 +0200
From: Christoph Hellwig <hch@....de>
To: Thadeu Lima de Souza Cascardo <cascardo@...onical.com>
Cc: linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org,
Sagi Grimberg <sagi@...mberg.me>, Jens Axboe <axboe@...com>,
Christoph Hellwig <hch@....de>,
Potnuri Bharat Teja <bharat@...lsio.com>,
Keith Busch <keith.busch@...el.com>,
Hannes Reinecke <hare@...e.com>,
"Martin K . Petersen" <martin.petersen@...cle.com>
Subject: Re: [PATCH] nvme: create 'paths' entries for hidden controllers
On Fri, Sep 28, 2018 at 04:17:20PM -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.
>
> Introducing the paths subdir and using that on initramfs-tools makes it
> possible to now boot a system with nvme multipath as root.
Do we need documentation how these paths links are supposed to work?
Who is going to parse them?
Powered by blists - more mailing lists