Skip to main content
NetApp Stage KB

Volume size and quotas remain after PVC and qtree deletion

Views:
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
SNAPX
Last Updated:

Applies to

Trident for Kubernetes/Openshift

Issue

As for the ontap-nas driver, when using the "retain" policy, Trident does not clean up the qtree or the quota on the qtree for ontap-nas-economy, when the PVC is deleted. However, with the ontap-nas-economy driver, when you delete the qtree, you free the space in the volume, but that does not automatically remove the quota, or downsize the volume.
This will cause the following errors on quota commands:
 
Additionally, this will also cause attempts at creating a new qtree volume for that backend, when space, according to quotas, doesn't fit the new PVC due to the leftover quotas that are no longer qtree backed. If the SVM was set with a maximum number of volumes that has already been reached, the following error will occur:
Cannot create volume. Reason: Maximum volume count for Vserver <SVM> reached.  Maximum volume count is <VOL_LIMIT>.

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.
Case Citation
2a0fef28-bd7a-4465-9fd2-65294bdf2db6