From: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: Xose Vazquez Perez <xose.vazquez@gmail.com>,
Martin Wilck <mwilck@suse.com>, DM-DEVEL ML <dm-devel@redhat.com>
Subject: [dm-devel] [PATCH] multipath-tools: add basic info on how to use multipath-tools with NVMe devices
Date: Mon, 28 Mar 2022 19:04:04 +0200 [thread overview]
Message-ID: <20220328170404.8565-1-xose.vazquez@gmail.com> (raw)
Cc: Martin Wilck <mwilck@suse.com>
Cc: Benjamin Marzinski <bmarzins@redhat.com>
Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>
Cc: DM-DEVEL ML <dm-devel@redhat.com>
Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
---
README.nvme | 12 ++++++++++++
1 file changed, 12 insertions(+)
create mode 100644 README.nvme
diff --git a/README.nvme b/README.nvme
new file mode 100644
index 00000000..70bf6b0d
--- /dev/null
+++ b/README.nvme
@@ -0,0 +1,12 @@
+To use Device Mapper/multipath-tools with NVMe devices,
+if the Native NVMe Multipath subsystem is enabled
+( "Y" in /sys/module/nvme_core/parameters/multipath ),
+it has to be disabled:
+
+echo "options nvme_core multipath=N" > /etc/modprobe.d/01-nvme_core-mp.conf
+regenerate the initramfs (dracut -f or update-initramfs) and reboot.
+
+Check that it is disabled(N) with:
+cat /sys/module/nvme_core/parameters/multipath
+or
+systool -m nvme_core -A multipath
--
2.35.1
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
next reply other threads:[~2022-03-28 17:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 17:04 Xose Vazquez Perez [this message]
2022-03-28 17:48 ` [dm-devel] [PATCH] multipath-tools: add basic info on how to use multipath-tools with NVMe devices Martin Wilck
2022-03-28 17:57 ` Xose Vazquez Perez
2022-04-01 10:20 ` Martin Wilck
2022-06-16 20:32 ` Xose Vazquez Perez
2022-06-17 6:48 ` Martin Wilck
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=20220328170404.8565-1-xose.vazquez@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=dm-devel@redhat.com \
--cc=mwilck@suse.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.