538 Implementing the IBM Storwize V7000 with IBM Spectrum Virtualize V8.2.1
Detailed states
The following sections describe the states that are portrayed to the user for Consistency 
Groups or relationships. They also describe information that is available in each state. The 
major states are designed to provide guidance about the available configuration commands.
InconsistentStopped
InconsistentStopped is a connected state. In this state, the master is accessible for read and 
write I/O, but the auxiliary is not accessible for read or write I/O. A copy process must be 
started to make the auxiliary consistent. This state is entered when the relationship or 
Consistency Group was InconsistentCopying and suffered a persistent error or received a 
stop command that caused the copy process to stop.
A start command causes the relationship or Consistency Group to move to the 
InconsistentCopying state. A stop command is accepted, but has no effect.
If the relationship or Consistency Group becomes disconnected, the auxiliary side makes the 
transition to InconsistentDisconnected. The master side changes to IdlingDisconnected.
InconsistentCopying
InconsistentCopying is a connected state. In this state, the master is accessible for read and 
write I/O, but the auxiliary is not accessible for read or write I/O. This state is entered after a 
start command is issued to an InconsistentStopped relationship or a Consistency Group. 
It is also entered when a forced start is issued to an Idling or ConsistentStopped relationship 
or Consistency Group. In this state, a background copy process runs that copies data from 
the master to the auxiliary volume.
In the absence of errors, an InconsistentCopying relationship is active, and the copy 
progress increases until the copy process completes. In certain error situations, the copy 
progress might freeze or even regress.
A persistent error or stop command places the relationship or Consistency Group into an 
InconsistentStopped state. A start command is accepted but has no effect. 
If the background copy process completes on a stand-alone relationship or on all 
relationships for a Consistency Group, the relationship or Consistency Group changes to the 
ConsistentSynchronized state.
If the relationship or Consistency Group becomes disconnected, the auxiliary side changes to 
InconsistentDisconnected. The master side changes to IdlingDisconnected.
ConsistentStopped
ConsistentStopped is a connected state. In this state, the auxiliary contains a consistent 
image, but it might be out-of-date in relation to the master. This state can arise when a 
relationship was in a ConsistentSynchronized state and experienced an error that forces a 
Consistency Freeze. It can also arise when a relationship is created with a 
CreateConsistentFlag set to TRUE.
Normally, write activity that follows an I/O error causes updates to the master, and the 
auxiliary is no longer synchronized. In this case, consistency must be given up for a period to 
reestablish synchronization. You must use a start command with the -force option to 
acknowledge this condition, and the relationship or Consistency Group changes to 
InconsistentCopying. Enter this command only after all outstanding events are repaired.