IBM Support

IT30520: FAILED SNAPSHOTS REFERENCES ARE NOT CLEANED UP BY THE VSNAP MAINTENANCE JOB

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Failed snapshots references appear not to have been cleaned up
    by the vSnap maintenance job.
    The command 'vsnap maint show' will display older snapshot
    entries as the following example :
    
    ID | TYPE     | NAME               | STATUS | CREATED    |
    STARTED    | ENDED
    ----------------------------------------------------------------
    -------------
     1 | snapshot | vpool1/fs1@snap123 | FAILED | 1567073347 |
    1568296336 | N/A
     2 | snapshot | vpool1/fs2@snap456 | FAILED | 1567073347 |
    1568406867 | N/A
    
    but there is further no trace of these snapshots as seen with
    the following commands :
    
    'zfs list -r -t snapshot -o
    name,used,lused,avail,ratio,creation'
    
    NAME                USED LUSED AVAIL RATIO CREATION
    none of the above snapshots is seen here
    
    'vsnap snapshot show'
    
    ID | PARENT ID | CREATED                | NAME
    ----------------------------------------------------------------
    -------
    none of the above snapshots is seen here
    
    ls -alR of the corresponding filespaces :
      /vsnap/vpool1/fs1/.zfs/snapshot/
      /vsnap/vpool1/fs2/.zfs/snapshot/
    
    will not list any of the above snapshots.
    
    This is only a local maintenance database entry that is left
    over and not being cleaned up by the vSnap maintenance job.
    It has no impact on operations.
    
    IBM Spectrum Protect Versions Affected:
    All supported IBM Spectrum Protect Plus 10.1.x versions
    
    Initial Impact: Low
    
    Additional Keywords: SPP, SPPLUS, TS002775367 , vsnap, snapshot,
    failed, leftover
    

Local fix

  • These entries can be manually cleaned up with the following
    procedure :
    On the vSnap host where the snapshots are not being deleted run
    the following commands:
    1. sudo sqlite3 /etc/vsnap/maint.db "delete from maint_session;"
    2. sudo systemctl restart vsnap-maintThis will purge the queue
    of pending deletions.
    After having restarted the service 'vcnap-maint', wait for a few
    minutes then run the command:
    'vsnap maint show'
    to monitor the queue and see if it shows any active/completed
    deletions.
    This may vary depending on the system's activity.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * IBM Spectrum Protect Plus level 10.1.4.                      *
    ****************************************************************
    * 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. Note that this is subject to change at the           *
    * discretion of IBM.                                           *
    ****************************************************************
    

Problem conclusion

  • The vsnap-maint service is responsible for reclaiming space
    freed by deleted snapshots. This service maintains a history of
    recent snapshot deletions which can be seen by running 'vsnap
    maint show'. If a snapshot deletion fails, it is retried later.
    In cases where the deletion initially fails and later succeeds,
    the history was not purged correctly. The failed attempts stayed
    in the history indefinitely.
    
    This is a cosmetic issue only. This history is for informational
    purposes only, it has no impact on functionality. It was caused
    by incorrect status checking while purging the history of old
    attempts.
    
    The problem has been resolved by correcting the status check to
    ensure that both successful as well as failed sessions are
    deleted from the history.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT30520

  • Reported component name

    SP PLUS

  • Reported component ID

    5737SPLUS

  • Reported release

    A14

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-10-07

  • Closed date

    2019-10-21

  • Last modified date

    2019-10-21

  • 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":"A14","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
30 January 2024