---
title: "Leveraging Trash Folder Access to Handle Deletions"
slug: "leveraging-trash-folder-access-to-handle-deletions-2-5"
updated: 2026-11-03T22:08:05Z
published: 2026-11-03T22:08:05Z
canonical: "docs.vastdata.com/leveraging-trash-folder-access-to-handle-deletions-2-5"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vastdata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Leveraging Trash Folder Access to Handle Deletions

VAST CSI Driver gains a substantial performance boost during volume deletions through the use of *Trash Folder Access*, a feature of VAST Cluster.

> [!NOTE]
> Note
> 
> VAST Cluster 4.7.0-SP6 or later is required for the VAST drivers to be able to use the Trash Folder Access feature.

When deleting a volume that resides on VAST Cluster 4.7.0-SP6 and later where the Trash Folder Access feature is enabled, the delete request is processed using the VAST REST API's `/folders/delete_folder/` endpoint. This means that the processing takes place locally on the VAST cluster.

VAST CSI Driver can delete either through Trash Folder Access, or by using a backward-compatibility mode which requires you to [dedicate](/develop/docs/en/configure-vast-cluster-for-vast-csi-driver-2-5#extra-configuration-steps-for-legacy-csi-local-mount-deletions) a virtual IP pool and a view policy for deletions through the `deletionVipPool` and `deletionViewPolicy` parameters in the VAST CSI Driver [Helm chart configuration file](/develop/docs/en/create-a-helm-chart-configuration-file-for-vast-csi-driver-2-5).

When deleting volumes that reside on a VAST Cluster version earlier than 4.7.0-SP6, or when Trash Folder Access is disabled for any reason, you still need to specify `deletionVipPool` and `deletionViewPolicy`.

> [!NOTE]
> Note
> 
> For deletions to succeed, the tenant in the deletion view policy (`deletionViewPolicy`) must match the tenant of the view policy (`viewPolicy`) specified for the storage class.