Skip to main content
NetApp Knowledge Base

CONTAP-477255: Cloud Tier Capacity Not Reclaimed After Volume Deletion

  1. Last updated
  2. Save as PDF
Views:
1
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

Issue

With FabricPool or Cloud Tiering enabled, space in the object store might not be reclaimed after a volume is deleted. Cloud garbage collection starts only when the amount of unreferenced object-store space reaches a minimum percentage of the aggregate’s used object-store capacity. When unreferenced space is below that percentage, garbage collection does not run, so objects belonging to the deleted volume remain in the object store.
Because those objects remain, the volume can remain in a partially deleted state and cannot be fully removed. Capacity billed by the object store is not reduced, which can prevent an expected reduction in cloud storage cost.
The condition is more likely when several volumes are tiered to the same aggregate and only one volume is deleted, because the unreferenced space from that volume can fall below the start threshold.

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.