All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: bvanassche@acm.org, yi.zhang@redhat.com, sagi@grimberg.me
Cc: Luis Chamberlain <mcgrof@kernel.org>,
	linux-block@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: can't run nvme-mp blktests
Date: Tue, 12 Apr 2022 17:24:04 -0700	[thread overview]
Message-ID: <YlYYJC/WUEsnI9Im@bombadil.infradead.org> (raw)

I do have CONFIG_NVME_MULTIPATH=y but I also have:

cat /etc/modprobe.d/nvme.conf 
options nvme_core multipath=N

And yet I always end up booting with:

cat /sys/module/nvme_core/parameters/multipath 
Y

So trying to run:

nvme_trtype=rdma ./check nvmeof-mp

I end up with the warning:

nvmeof-mp/***                                                [not run]
    CONFIG_NVME_MULTIPATH has been set in .config and multipathing has been enabled in the nvme_core kernel module

Are there times where one cannot disable multipath? I'm not using
any nvme drive at boot, but I do use one for a random data parition.

Any tips?

  Luis

             reply	other threads:[~2022-04-13  0:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13  0:24 Luis Chamberlain [this message]
2022-04-13  3:02 ` can't run nvme-mp blktests Yi Zhang
2022-04-13 17:38   ` Luis Chamberlain
2022-04-13  4:53 ` Christoph Hellwig
2022-04-13 17:38   ` Luis Chamberlain
2022-04-13 17:41     ` Christoph Hellwig
2022-04-13 18:12       ` Luis Chamberlain
2022-04-15  5:22         ` Christoph Hellwig
2022-04-13 22:46       ` Bart Van Assche
2022-04-15  5:20         ` Christoph Hellwig
2022-04-15  5:58           ` Chaitanya Kulkarni
2022-04-15 17:59             ` Luis Chamberlain
2022-04-15 18:09               ` Bart Van Assche
2022-04-20 10:36                 ` Hannes Reinecke
2022-04-21 17:56                 ` Luis Chamberlain
2022-04-15 18:06             ` Bart Van Assche
2022-04-20 10:29               ` Hannes Reinecke
2022-04-13  5:53 ` Bart Van Assche
2022-04-13 18:08   ` Luis Chamberlain

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=YlYYJC/WUEsnI9Im@bombadil.infradead.org \
    --to=mcgrof@kernel.org \
    --cc=bvanassche@acm.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    --cc=yi.zhang@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.