Skip to main content
NetApp Knowledge Base

Excessive Trident autogrow events after VMware to OpenShift migration

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

Applies to

  • Trident
  • OpenShift (OCP)
  • Commvault
  • VMware
  • Migration Toolkit for Virtualization (MTV)
  • Autogrow 

Issue

  • After migrating Trident NFS storage class VMs from VMware to an OpenShift Trident iSCSI storage class, thin-provisioned persistent volumes (PVs) become fully allocated, with disk usage inflating from actual data size (e.g., ~10GB) to the full disk size (e.g., 90–100GB). Excessive autogrow event messages are logged for affected PVs, such as:

MountVolume.NodeExpandVolume succeeded for volume "pvc-.......-121212121abc"

MountVolume.NodeExpandVolume succeeded for volume "pvc-.......-121212121efg"

  • Events are logged tens of thousands of times over a few days, but PV sizes remain constant
  • Customers observes operational overhead from excessive event logging and potential backup/recovery delays

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.