Skip to main content
NetApp Knowledge Base

Unable to Delete Kubernetes Volume Snapshots on ONTAP – “Busy/Locked” Errors with Trident CSI

  1. Last updated
  2. Save as PDF
Views:
24
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
SNAPX
Last Updated:

Applies to

  • Kubernetes clusters with Trident-managed PVs/PVCs
  • Third-party backup tools (e.g., Commvault) integrated with Kubernetes

Issue

When attempting to delete Kubernetes volume snapshots managed by Trident on a NetApp ONTAP backend, the operation fails with ONTAP returning “busy” or “locked” errors. This results in:

  • Stale/orphaned snapshots that cannot be deleted (even manually).
  • Backup jobs (e.g., Commvault) failing or stalling due to inability to clean up old snapshots, causing space to fill up and preventing new backups from triggering.
  • Kubernetes PVC provisioning and other volume operations experiencing delays or timeouts.
  • Example log output: 
    Failed to delete snapshot: ONTAP reports snapshot is busy/locked due to dependent clone(s)
MountVolume.MountDevice failed for volume "pvc-xxxx": rpc error: code = DeadlineExceeded desc = context deadline exceeded
  • Trident logs show repeated snapshot delete failures and ONTAP error codes for busy/locked objects.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.