
54
shows that every device’s path 0 (those corresponding to device
filenames beginning
c7) have a Status designation of Bad.
Figure 5-6 setsp -a Output after the Failed Path Is Detected
Recovering from a Failure
Path failures generate a lot of output, resulting primarily from the
disk driver’s attempts at error recovery.
Finally, when the cable is plugged back in, SVA Path will detect
that the primary I/O path for
spd0 is back to normal and redirect
data over that path (Figure 5-7, “The Failback Event”).
Figure 5-7 The Failback Event
The other paths are returned to Status Good, as well.
The output of
setsp -a will return to normal (Figure 5-1, on
page 51).
# setsp -a
===============================================================================
spd Path/disk Status Primary Exclude Buf Balance RtrCnt RtrDly FailBack
===============================================================================
0 c6t0d0 Good X 32 0 20 3000 1
c7t0d0 Good
spd0 = c86t0d0 ID = "STK 9500 0000000010390000"
===============================================================================
1 c6t0d1 Bad X 32 0 20 3000 1
c7t0d1 Good
spd1 = c86t0d1 ID = "STK 9500 0000000010390001"
===============================================================================
2 c6t0d2 Bad X 32 0 20 3000 1
c7t0d2 Good
spd2 = c86t0d2 ID = "STK 9500 0000000010390002"
===============================================================================
Jun 30 15:29:31 n4000 vmunix: spd1: path 0 ok
Jun 30 15:29:31 n4000 vmunix: spd2: path 0 ok
Jun 30 15:29:31 n4000 vmunix: spd3: path 0 ok
Jun 30 15:29:31 n4000 vmunix: spd1: path failover from 1 to 0.
Comments to this Manuals