Veritas Storage Foundation 5.1 SP1 for Oracle RAC Administrator"s Guide (5900-1512, April 2011)

Table 1-2
I/O fencing scenarios (continued)
Operator actionNode B: What
happens?
Node A: What
happens?
Event
Verify private
networks function
and restart Node A.
Node B loses
heartbeats with Node
A, and races for a
majority of
coordinator disks.
Node B wins race for
coordinator disks and
ejects Node A from
shared data disks.
Node A is extremely
busy for some reason
or is in the kernel
debugger.
When Node A is no
longer hung or in the
kernel debugger, any
queued writes to the
data disks fail
because Node A is
ejected. When Node
A receives message
from GAB about
being ejected, it
panics and removes
itself from the
cluster.
Node A hangs.
Overview of Veritas Storage Foundation for Oracle RAC
About preventing data corruption with I/O fencing
50