Skip to main content
NetApp Knowledge Base

Trident Automatic Volume Expansion Not Triggering as Expected for PVCs

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

Applies to

  • NetApp Trident 26.02
  • Kubernetes/OpenShift environments using Trident with Automatic Volume Expansion (Autogrow) enabled
  • Persistent Volume Claims (PVCs) with Trident Autogrow Policy applied

Issue

Persistent Volume Claims (PVCs) configured to use Trident’s Automatic Volume Expansion (Autogrow) do not expand as expected when reaching the usage threshold. 

When writing a file larger than the PVC size (e.g., writing 2GB to a 1GB PVC), the operation fails with No space left on device. The PVC may expand only after the failure, or not at all.

 

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.