Managing I/O In Error Situations - Novell LINUX ENTERPRISE SERVER 10 SP2 - STORAGE ADMINISTRATION GUIDE 05-15-2009 Administration Manual

\_ round-robin 0 [active][first]
\_ 1:0:1:2 sdav 66:240
\_ 0:0:1:2 sdr
\_ round-robin 0 [enabled]
\_ 1:0:0:2 sdag 66:0
\_ 0:0:0:2 sdc
For each device, it shows the device's ID, size, features, and hardware handlers.
Paths to the device are automatically grouped into priority groups on device discovery. Only one
priority group is active at a time. For an active/active configuration, all paths are in the same group.
For an active/passive configuration, the passive paths are placed in separate priority groups.
The following information is displayed for each group:
Scheduling policy used to balance I/O within the group, such as round-robin
Whether the group is active, disabled, or enabled
Whether the group is the first (highest priority) group
Paths contained within the group
The following information is displayed for each path:
The physical address as host:bus:target:lun, such as 1:0:1:2
Device node name, such as
Major:minor numbers
Status of the device

5.13 Managing I/O in Error Situations

You might need to configure multipathing to queue I/O if all paths fail concurrently. In certain
scenarios, where the driver, the HBA, or the fabric experiences spurious errors, it is advisable that
DM-MP be configured to queue all I/O where those errors lead to a loss of all paths, and never
propagate errors upwards. Because this leads to I/O being queued indefinitely unless a path is
reinstated, make sure that
might be stalled indefinitely on the affected multipathed device, until reboot or until you manually
return to failover instead of queuing.
To test the scenario:
1 In a terminal console, log in as the
2 Activate queuing instead of failover for the device I/O by entering:
dmsetup message device_ID 0 queue_if_no_path
Replace the device_ID with the ID for your device. For example, enter:
dmsetup message 3600601607cf30e00184589a37a31d911 0 queue_if_no_path
3 Return to failover for the device I/O by entering:
dmsetup message device_ID 0 fail_if_no_path
This command immediately causes all queued I/O to fail.
Replace the device_ID with the ID for your device. For example, enter:
dmsetup message 3600601607cf30e00184589a37a31d911 0 fail_if_no_path
72 SLES 10 SP2: Storage Administration Guide
[ready ][active]
65:16 [ready ][active]
[ready ][active]
8:32 [ready ][active]
sda
is running and works for your scenario. Otherwise, I/O
multipathd
user.
root