Skip to main content
NetApp Stage KB

Failed to provision new volumes using trident after number of volumes on SVM reached to maximum limit

Views:
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
SNAPX
Last Updated:

Applies to

  • Trident
  • Kubernetes or Openshift

Issue

  • Number of volumes reached the maximum on the SVM on the ONTAP storage system:
    <BACKEND_NAME> pool <AGGR_NAME>/<AGGR_NAME>; error creating volume <PREFIX>_pvc_<PVC-UUID>: API status: failed, Reason: Cannot create volume. Reason: Maximum volume count for Vserver <SVM_NAME> reached.  Maximum volume count is 480 (*). , Code: 13001
  • Some volumes were deleted to bring the number volumes on storage below maximum limit.
  • Provision of new volume using Trident still failed for some time.

 

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.
9ae2bc6a-120d-4f45-9a89-939b051dc5e0