Resolving Stalled I/O; Additional Information; What's Next; Section 5.16, "Resolving Stalled I/O - Novell LINUX ENTERPRISE SERVER 10 - STORAGE ADMINISTRATION GUIDE 7-2007 Administration Manual

Replace the mapname (such as 3600601607cf30e00184589a37a31d911) with the map
name for the device.
This command immediately causes all queued I/O to fail and propagates the error to the calling
application.

5.16 Resolving Stalled I/O

If all paths fail concurrently and I/O is queued and stalled, do the following:
1 Enter the following command at a terminal console prompt:
dmsetup message mapname 0 fail_if_no_path
Replace mapname with the correct map name, such as
3600601607cf30e00184589a37a31d911. This causes all queued I/O to fail and
propagates the error to the calling application.
2 Reactivate queueing by entering the following command at a terminal console prompt:
dmsetup message mapname 0 queue_if_no_path

5.17 Additional Information

For more information about configuring and using multipath I/O on SUSE Linux Enterprise Server,
see How to Setup/Use Multipathing on SLES (http://support.novell.com/techcenter/sdb/en/2005/04/
sles_multipathing.html) in the Novell Support Knowledgebase.

5.18 What's Next

If you want to use software RAIDs, create and configure them before you create file systems on the
devices. For information, see the following:
Chapter 6, "Managing Software RAIDs with EVMS," on page 59
Chapter 7, "Managing Software RAIDs 6 and 10 with mdadm," on page 81
Managing Multipath I/O for Devices 57