第 8 章 Troubleshooting DM Multipath


Troubleshoot multipath configuration issues by checking daemon status, queue_if_no_path feature problems, and using the multipathd interactive console for diagnostics.

The following issues may result in a slow or non-functioning multipath configuration:

The multipath daemon is not running
If you find you have trouble implementing a multipath configuration, ensure that the multipathd daemon is running, as described in Configuring DM Multipath. The multipathd daemon must be running to use multipathed devices.
Issues with queue_if_no_path feature
If a multipath device is configured with the features "1 queue_if_no_path" option, then any process that issues I/O hangs until one or more paths are restored.

8.1. Troubleshooting issues with queue_if_no_path feature

Resolve I/O hangs from queue_if_no_path by setting no_path_retry N in /etc/multipath.conf, limiting retries when all paths fail. You can also disable queueing at runtime for specific LUNs to prevent applications from hanging during path outages.

Procedure

  1. Disable queueing:

    • For a specific device:

      # multipathd disablequeueing map device
    • For all devices:

      # multipathd disablequeueing maps

      After you disable queueing, it will remain disabled until you restart or reload multipathd.

  2. Reset queueing to a previous value:

    • For a specific device:

      # multipathd restorequeueing map device
    • For all devices:

      # multipathd restorequeueing maps
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2026 Red Hat
返回顶部