Chapter 4. Enabling multipathing on NVMe devices
You can multipath Non-volatile Memory Express™ (NVMe™) devices that are connected to your system over a fabric transport, such as Fibre Channel (FC). You can select between multiple multipathing solutions.
4.1. Native NVMe multipathing and DM Multipath Copy linkLink copied to clipboard!
Non-volatile Memory Express™ (NVMe™) devices support a native multipathing functionality. When configuring multipathing on NVMe, you can select between the standard DM Multipath framework and the native NVMe multipathing.
Both DM Multipath and native NVMe multipathing support the Asymmetric Namespace Access (ANA) multipathing scheme of NVMe devices. ANA identifies optimized paths between the controller and the host, and improves performance.
When native NVMe multipathing is enabled, it applies globally to all NVMe devices. It can provide higher performance, but does not contain all of the functionality that DM Multipath provides. For example, native NVMe multipathing supports only the numa
and round-robin
path selection methods.
Red Hat recommends that you use DM Multipath in Red Hat Enterprise Linux 8 as your default multipathing solution.
4.2. Enabling native NVMe multipathing Copy linkLink copied to clipboard!
The default kernel setting for the nvme_core.multipath
option is set to N
, which means that the native Non-volatile Memory Express™ (NVMe™) multipathing is disabled. You can enable native NVMe multipathing using the native NVMe multipathing solution.
Prerequisites
- The NVMe devices are connected to your system. For more information, see Overview of NVMe over fabric devices.
Procedure
Check if native NVMe multipathing is enabled in the kernel:
cat /sys/module/nvme_core/parameters/multipath
# cat /sys/module/nvme_core/parameters/multipath
Copy to Clipboard Copied! Toggle word wrap Toggle overflow The command displays one of the following:
N
- Native NVMe multipathing is disabled.
Y
- Native NVMe multipathing is enabled.
If native NVMe multipathing is disabled, enable it by using one of the following methods:
Using a kernel option:
Add the
nvme_core.multipath=Y
option to the command line:grubby --update-kernel=ALL --args="nvme_core.multipath=Y"
# grubby --update-kernel=ALL --args="nvme_core.multipath=Y"
Copy to Clipboard Copied! Toggle word wrap Toggle overflow On the 64-bit IBM Z architecture, update the boot menu:
zipl
# zipl
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Reboot the system.
Using a kernel module configuration file:
Create the
/etc/modprobe.d/nvme_core.conf
configuration file with the following content:options nvme_core multipath=Y
options nvme_core multipath=Y
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Back up the
initramfs
file:cp /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).bak.$(date +%m-%d-%H%M%S).img
# cp /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).bak.$(date +%m-%d-%H%M%S).img
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Rebuild the
initramfs
:dracut --force --verbose
# dracut --force --verbose
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Reboot the system.
Optional: On the running system, change the I/O policy on NVMe devices to distribute the I/O on all available paths:
echo "round-robin" > /sys/class/nvme-subsystem/nvme-subsys0/iopolicy
# echo "round-robin" > /sys/class/nvme-subsystem/nvme-subsys0/iopolicy
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Optional: Set the I/O policy persistently using
udev
rules. Create the/etc/udev/rules.d/71-nvme-io-policy.rules
file with the following content:ACTION=="add|change", SUBSYSTEM=="nvme-subsystem", ATTR{iopolicy}="round-robin"
ACTION=="add|change", SUBSYSTEM=="nvme-subsystem", ATTR{iopolicy}="round-robin"
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Verification
Verify if your system recognizes the NVMe devices. The following example assumes you have a connected NVMe over fabrics storage subsystem with two NVMe namespaces:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow List all connected NVMe subsystems:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Check the active transport type. For example,
nvme0 fc
indicates that the device is connected over the Fibre Channel transport, andnvme tcp
indicates that the device is connected over TCP.If you edited the kernel options, verify if native NVMe multipathing is enabled on the kernel command line:
cat /proc/cmdline BOOT_IMAGE=[...] nvme_core.multipath=Y
# cat /proc/cmdline BOOT_IMAGE=[...] nvme_core.multipath=Y
Copy to Clipboard Copied! Toggle word wrap Toggle overflow If you changed the I/O policy, verify if
round-robin
is the active I/O policy on NVMe devices:cat /sys/class/nvme-subsystem/nvme-subsys0/iopolicy round-robin
# cat /sys/class/nvme-subsystem/nvme-subsys0/iopolicy round-robin
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
4.3. Enabling DM Multipath on NVMe devices Copy linkLink copied to clipboard!
You can enable DM Multipath on connected NVMe devices by disabling native NVMe multipathing.
Prerequisites
- The NVMe devices are connected to your system. For more information, see Overview of NVMe over fabric devices.
Procedure
Check if the native NVMe multipathing is disabled:
cat /sys/module/nvme_core/parameters/multipath
# cat /sys/module/nvme_core/parameters/multipath
Copy to Clipboard Copied! Toggle word wrap Toggle overflow The command displays one of the following:
N
- Native NVMe multipathing is disabled.
Y
- Native NVMe multipathing is enabled.
If the native NVMe multipathing is enabled, disable it by using one of the following methods:
Using a kernel option:
Remove the
nvme_core.multipath=Y
option from the kernel command line:grubby --update-kernel=ALL --remove-args="nvme_core.multipath=Y"
# grubby --update-kernel=ALL --remove-args="nvme_core.multipath=Y"
Copy to Clipboard Copied! Toggle word wrap Toggle overflow On the 64-bit IBM Z architecture, update the boot menu:
zipl
# zipl
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Reboot the system.
Using a kernel module configuration file:
-
Remove the
nvme_core multipath=Y
option line from the/etc/modprobe.d/nvme_core.conf
file, if it is present. Back up the
initramfs
file:cp /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).bak.$(date +%m%d-%H%M%S).img
# cp /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).bak.$(date +%m%d-%H%M%S).img
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Rebuild the
initramfs
:cp /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).bak.$(date +%m-%d-%H%M%S).img dracut --force --verbose
# cp /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).bak.$(date +%m-%d-%H%M%S).img # dracut --force --verbose
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Reboot the system.
-
Remove the
Enable DM Multipath:
systemctl enable --now multipathd.service
# systemctl enable --now multipathd.service
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Distribute I/O on all available paths. Add the following content in the
/etc/multipath.conf
file:Copy to Clipboard Copied! Toggle word wrap Toggle overflow NoteThe
/sys/class/nvme-subsystem/nvme-subsys0/iopolicy
configuration file has no effect on the I/O distribution when DM Multipath manages the NVMe devices.Reload the
multipathd
service to apply the configuration changes:multipath -r
# multipath -r
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Verification
Verify if the native NVMe multipathing is disabled:
cat /sys/module/nvme_core/parameters/multipath N
# cat /sys/module/nvme_core/parameters/multipath N
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Verify if DM multipath recognizes the nvme devices:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow