Error Message

The returned message while performing the snap refresh:

# vxsnap -g crmdg refresh SNAP-mirra
VxVM vxvol ERROR V-5-1-1225 Volume SNAP-mirra is locked by another utility
 

This customer tried to remove the lock on the snap volume.

#vxmend -g crmdg -r clear all SNAP-mirra

Then, the following message is returned while tried to disassociate a full-sized instant volume that is associated the volume.

#vxsnap -g crmdg dis SNAP-mirra
VxVM vxsnap ERROR V-5-1-1225 Volume mirra is locked by another utility

We could see that tutil0 flag is set at both source and snap volume in the output of the vxprint -m. In detail, The tutil0 flag is "INST_SRC1" at source and "SNAP_REFRESH" at snap volume. It indicated that the lock is set when a a recovery or administration operation within Volume Manager is interrupted with some reasons.

The output of the vxprint -m before trying to remove a lock on the volume:

# vxprint -g crmdg -m arch
vol  arch
       tutil0="INST_SRC1 <<<<
       tutil1="
       tutil2="
       kstate=ENABLED
      ...
       putil0="
       putil1="
       putil2="
       state="ACTIVE
       
# vxprint -g crmdg -m SNAP-arch
vol  SNAP-arch
       tutil0="SNAP_REFRESH <<<
       tutil1="
       tutil2="
       kstate=DISABLED
       ...
       putil0="
       putil1="
       putil2="
       state="ACTIVE

Above of values are:

"INST_SRC": Volume is being used as source of the snapshot operation

"SNAP_REFRESH": Volume is target of a refresh operation

After clearing a lock on the snap volume, The lock is still exist on the source volume.

The output of the vxprint -m after trying to remove a lock on the volume.

# vxprint -g crmdg -m mirra
vol  mirra
        tutil0="INST_SRC1         <<<<    
        tutil1="
        tutil2="
        kstate=ENABLED
        ..
         putil0="
  putil1="
  putil2="
        state="ACTIVE
       
# vxprint -g crmdg -m SNAP-mirra
vol  SNAP-mirra
        tutil0="
        tutil1="
        tutil2="
        kstate=DISABLED
       ...
        putil0="
        putil1="
        putil2="
       state="ACTIVE

First of all, this customer should check that no parrallel operation is occuring on the volume as following ways:

# ps -ef | grep vx

# vxtask list

If no parallel operation is occuring, the previous operation is failed prematurely, and the tutil field and the state field on the volume can identify which operation is failed.

So, this customer can clear the tutil field  and the volume will be ready to accept further operation again. As we checked at earlier step, the tutil field is still set on the source volume.

To clear the tutil field, use the following command:

# vxmend -g clear tutil

After clearing the tutil flag, snap refresh can be performed again

vxsnap -g refresh

The problem this customer has is a lack of system resource when performing the snap refresh given out the message as belows: VxVM VVR vxsnap ERROR V-5-1-505 Could not fork: Not enough space+ vxsnap -g crmdg refresh SNAP-mirra
VxVM vxvol ERROR V-5-1-2321 Cannot lock into memory: Not enough space This condition of their system is resulted in an abnormal interruption of the snap operation and the following error is returned while trying to do the snap refresh operation. VxVM vxvol ERROR V-5-1-1225 Volume SNAP-mirra is locked by another utility