Use the stopfcmap command to stop all processing that is associated with a FlashCopy mapping that is in one of the following processing states: prepared, copying, stopping, or suspended.


stopfcmap [ { -force | -split } ] fc_map_id_or_name


(Optional) Specifies that all processing that is associated with the designated mapping be stopped immediately.
Note: When you use this parameter, all FlashCopy mappings that depend on this mapping (as listed by the lsfcmapdependentmaps command) are also stopped.
If the -force parameter is not specified, the command is rejected if the target volume of the FlashCopy mapping is the primary in a relationship which is mirroring I/O:
  • consistent_synchronized
  • consistent_copying
  • inconsistent_copying

If the -force parameter is specified to a FlashCopy mapping whose target volume is also in a Metro Mirror or Global Mirror relationship, the relationship stops. If a remote copy relationship associated with the target was mirroring I/O when the map was copying, it might lose its difference recording capability and require a full resychronization on a subsequent restart.

(Optional) Breaks the dependency on the source volume of any mappings that are also dependent on the target disk. This parameter can only be specified when stopping a map that has progress of 100 as shown by the lsfcmap command.
(Required) Specifies the name or ID of the mapping to stop.


This command stops a single mapping. If the copy process is stopped, the target disk becomes unusable unless it already contained a complete image of the source (that is, unless the map had a progress of 100 as shown by the lsfcmap command). Before you can use the target disk, the mapping must once again be prepared and then reprocessed (unless the target disk already contained a complete image).

Only stand-alone mappings can be stopped using the stopfcmap command. Mappings that belong to a consistency group must be stopped using the stopfcconsistgrp command.

If the mapping is in the idle_or_copied state, the stopfcmap command has no effect and the mapping stays in the idle_or_copied state.
Note: Before Lenovo Storage V series 4.2.0, the stopfcmap command always changed the mapping state to stopped and took the target volume offline. This change can break scripts that depend on the previous behavior.

The split option can be used when the mapping has progress of 100. It removes the dependency of any other mappings on the source volume. It might be used prior to starting another FlashCopy mapping whose target disk is the source disk of the mapping being stopped. Once the mapping has been stopped with the split option, the other mapping could then be started without the restore option.

Note: Maps that are rc_controlled are not shown in the view when this command is specified.
Remember: If the source volume is in an active-active relationship then the FlashCopy mapping can only be stopped if the information on the source volume is current, or an older copy to which access has been provided by specifying:
stoprcrelationship -access
A current volume in an active-active relationship is the primary copy, or the secondary copy when the relationship's state is consistent_syncronized.

An invocation example

stopfcmap testmapone

The resulting output

No feedback