IBM Support

IT32164: VSNAP CLONED VOLUME NOT CLEANED UP AFTER 'INSTANT ACCESS' RESTORED DISK FAILED TO 'MAKE PERMANENT'

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When the instant access restore of a single disk from a VM
    completed successfully and a subsequent 'make permanent'
    operation failed, the cloned vSnap volume might fail to cleanup
    under certain circumstances. One example when this issue can be
    seen is a full destination datastore where the disk is moved to.
    
    
    When running vsnap volume show on the vsnap host, the following
    can be seen:
    
    ID | TYPE       | POOL | IS CLONE | TOTAL    | FREE    ...
    ----------------------------------------------------------
    1  | filesystem | 1    | No       | 168.00TB | 157.00TB...
    2  | filesystem | 1    | No       | 168.00TB | 157.00TB...
    44 | filesystem | 1    | Yes      | 168.00TB | 157.00TB...
    46 | filesystem | 1    | Yes      | 168.00TB | 157.00TB...
    
    As seen in above extract, volume 44 and 46 are cloned volumes,
    used for a restore operation.
    
    Looking in the Joblog from the failed restore job, the volume
    that is not expected can be identified:
    DETAIL,1583251642436,Tue 3 Mar 2020 17:07:22
    CET,2,CTGGA1307,Mounted volume
    (SPP_1067_1583747580145_00_spp_1019_2103_16d1f751688__group0_70_
    ) to NFS path (/vsnap/vpool1/fs44)
    
    The NFS path holds the vSnap ID that failed the cleanup. The
    Joblog does however not show any failure or other reference
    trying to remove the volume.
    
    IBM Spectrum Protect Plus Versions Affected:
    IBM Spectrum Protect Plus 10.1.x
    
    Initial Impact: Medium
    
    Additional Keywords: SPP, SPPlus, TS003454504
    

Local fix

  • Identify the cloned volume that is not needed any more.
    Run following on the vSnap:
    vsnap volume delete --id <id from cloned volume> --force
    
    Running with the force option will also cleanup any left over
    NFS shares.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * IBM Spectrum Protect Plus level 10.1.5                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See ERROR DESCRIPTION                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fixing level when available. This problem is currently *
    * projected to be fixed in IBM Spectrum Protect Plus level     *
    * 10.1.5.2199 and 10.1.6. Note that this is subject to change  *
    * at the discretion of IBM.                                    *
    ****************************************************************
    

Problem conclusion

  • For some vMotion or VM migrate failure conditions the job was
    marked failed instead of resource active. When it is resource
    active there will be an option to retry or cleanup.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT32164

  • Reported component name

    SP PLUS

  • Reported component ID

    5737SPLUS

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-03-23

  • Closed date

    2020-04-01

  • Last modified date

    2020-04-01

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    SP PLUS

  • Fixed component ID

    5737SPLUS

Applicable component levels

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSNQFQ","label":"IBM Spectrum Protect Plus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A10","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
31 January 2024