From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keith Busch Subject: Re: [PATCH 1/2] Don't blacklist nvme Date: Wed, 15 Feb 2017 12:24:02 -0500 Message-ID: <20170215172402.GA16197@localhost.localdomain> References: <1487107154-24883-1-git-send-email-keith.busch@intel.com> <941dc20e-47ba-5b9d-5082-a87ff1530cb6@sandisk.com> <20170214230023.GA1148@localhost.localdomain> <20170215145721.GB4241@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20170215145721.GB4241@infradead.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Christoph Hellwig Cc: Bart Van Assche , dm-devel@redhat.com List-Id: dm-devel.ids On Wed, Feb 15, 2017 at 06:57:21AM -0800, Christoph Hellwig wrote: > On Tue, Feb 14, 2017 at 06:00:23PM -0500, Keith Busch wrote: > > Good point. I was unknowingly running with CONFIG_SCSI_DH disabled, > > and blissfully unaware of its existence! After enabling that option, > > I see what you mean. > > Someone needs to fix that crash ASAP. I though Hannes had patches for > them a long time ago in the SuSE tree, but they never went anywhere. Adding Hannes. I can work around this by setting the parameters from multipath-tools specific to NVMe, but that seems worng. Blindly calling scsi specific directly from dm-mpath isn't a good idea.