Skip to main content
NetApp Knowledge Base

Trident Can't re-size PVCs when a manually created clone for the volume exists

  1. Last updated
  2. Save as PDF
Views:
73
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:

Applies to

Trident

Issue

Trident cannot re-size PVCs when a manually created clone for the underlying volume exists.
  • Trident will show the correct size of the ONTAP volume:
$ ./tridentctl get volume pvc-68e3ae8d-56c9-4c9c-87eb-ffad5ea0602e -n trident
|                   NAME                   |  SIZE   |
+------------------------------------------+---------+
| pvc-ab77xxxxx-fxxx-4yyy-bxxx-6c1yyyyyyy | 250 GiB  |
  • The Persistent Volume (PV) and the ONTAP volume size will show the correct re-sized volume.  
# kubectl get pv 
pvc-ab77xxxxx-fxxx-4yyy-bxxx-6c1yyyyyyyy   250Gi
  • The Persistent Volume Claim will show the incorrect volume size.
# kubectl get pvc 
pvc_claim_example   pvc-ab77xxxxx-fxxx-4yyy-bxxx-6c1yyyyyyy   200Gi
  • Viewing the file system from a mount command of the volume,  (ie. running 'ls' or 'df' command) will also show the incorrect FileSystem size.

 

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.