Skip to main content
NetApp Knowledge Base

Trident fails resizing a PVC due to volume size too large for the clone source

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

Applies to

  • Trident for Kuberneets and Openshift
  • ontap-nas driver

Issue

When the PV's ONTAP volume is larger than the PVC size, and has a clone, the PVC resize fails with the following message:
requested PVC size '10995116277760' is too large for the clone source '10871334256640'
However, Trident's trident-controller log shows that the error was really the following:
unable to resize the volume: unsupported capacity range; effective volume size 21990232555520 including any snapshot reserve is less than the existing volume size 22183062540288

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.