このコンテンツは選択した言語では利用できません。
5.5. device-mapper-multipath
The device-mapper-multipath packages provide tools to manage multipath devices using the device-mapper multipath kernel module.
- When using
dm-multipath, iffeatures "1 queue_if_no_path"is specified in/etc/multipath.confthen any process that issues I/O will hang until one or more paths are restored.To avoid this, setno_path_retry [N]in/etc/multipath.conf(where[N]is the number of times the system should retry a path). When you do, remove thefeatures "1 queue_if_no_path"option from/etc/multipath.confas well.If you need to use"1 queue_if_no_path"and experience the issue noted here, usedmsetupto edit the policy at runtime for a particular LUN (i.e. for which all the paths are unavailable).To illustrate: rundmsetup message [device] 0 "fail_if_no_path", where[device]is the multipath device name (e.g.mpath2; do not specify the path) for which you want to change the policy from"queue_if_no_path"to"fail_if_no_path". (BZ#419581) - When a LUN is deleted on a configured storage system, the change is not reflected on the host. In such cases,
lvmcommands will hang indefinitely whendm-multipathis used, as the LUN has now become stale.To work around this, delete all device andmpathlink entries in/etc/lvm/.cachespecific to the stale LUN.To find out what these entries are, run the following command:ls -l /dev/mpath | grep [stale LUN]For example, if[stale LUN]is 3600d0230003414f30000203a7bc41a00, the following results may appear:lrwxrwxrwx 1 root root 7 Aug 2 10:33 /3600d0230003414f30000203a7bc41a00 -> ../dm-4 lrwxrwxrwx 1 root root 7 Aug 2 10:33 /3600d0230003414f30000203a7bc41a00p1 -> ../dm-5
This means that 3600d0230003414f30000203a7bc41a00 is mapped to twompathlinks:dm-4anddm-5.As such, the following lines should be deleted from/etc/lvm/.cache:/dev/dm-4 /dev/dm-5 /dev/mapper/3600d0230003414f30000203a7bc41a00 /dev/mapper/3600d0230003414f30000203a7bc41a00p1 /dev/mpath/3600d0230003414f30000203a7bc41a00 /dev/mpath/3600d0230003414f30000203a7bc41a00p1
- Running the
multipathcommand with the-lloption can cause the command to hang if one of the paths is on a blocking device. Note that the driver does not fail a request after some time if the device does not respond.This is caused by the cleanup code, which waits until the path checker request either completes or fails. To display the currentmultipathstate without hanging the command, usemultipath -linstead. (BZ#214838)
