Sometimes FMR (Full Mirror Resync) Snapshot objects within VxVM leave stale unremovable objects. By default vxsnap or vxedit are unable to remove these type of objects.
To verify the object is stale use the command "vxprint -g -m". 

For example:


# vxprint -g ibs3dg -m
dco hitvol1_dco
tutil0="
tutil1="
tutil2="
parent_vol=hitvol1
log_vol=hitvol1_dcl
comment="DCO for hitvol1
rid=0.295228
putil0="
putil1="
putil2="
p_flag_move=off
badlog=on <<< badlog flag is on, badlog should be equal to off>>>
parent_vol_rid=0.1043
log_vol_rid=0.295221
sp_num=1
regionsz=128
version=20
drl=on
sequentialdrl=off
drllogging=off
snap=hitvol1_cpmap


1. Contact support for a special vxedit binary that allows cpmap objects to be removed.
2. Download special vxedit binary from the support representative.
3. Do not replace the default vxedit binary with this special vxedit binary.
4. Use the special vxedit binary to remove "sp" object from data volume for example:
# vxprint -qtrg testdg |grep cpmap
sp parentvol_cpmap parentvol parentvol_dco
^^
# /tmp/vxedit-special-5.0mp3rp3-aix5.3 -g testdg -f rm parentvol_cpmap

5. Once finished, remove the special vxedit binary from the system incase it is used by accident in the future.Or upgrade the latest VxVM version on top of 5.1SP1* to avoid the similar issue


 

How to remove cpmap objects within VxVM (Veritas Volume Manager) when vxedit or vxsnap errors with the following message "VxVM vxedit ERROR V-5-1-10048 parentvol_cpmap is a snap record, operation not allowed"

ETrack: 850816; 1715204