Description of problem:
This bug addresses a problem with the fix for bug 186004 - specifically when
considering cluster mirroring.
Problem statement: cluster mirroring log server does not get proper notification
when a region goes out-of-sync due to a failed write.

The original bug (186004) addressed the issue that the mirror log did not
properly handle the sync status of a region where a write failed to some (but
not all) of the mirror devices.  However, it used a mechanism to notify the
logging code that was only suitable to single machine mirroring.

For cluster mirroring, it is not acceptable to perform a suspend/resume cycle to
make the logging code pick up new out-of-sync regions.  This is because a
machine that does the suspend/resume cycle may not be the machine acting as the
cluster log server.  A more direct (and correct) method of informing the logging
code must be used when a region goes out-of-sync due to write failures.

This more direct method is done by replacing the suspend/resume cycle with a
call to complete_resync_work(/*failure*/).  By going this route, we are using
the action of the function to get the desired result, rather that getting the
desired result as a side effect.

Version-Release number of selected component (if applicable):
RHEL4 U4