---
name: containers-ts-storage-vpc-file-snapshot-delete
title: Why can't I delete my File Storage for VPC snapshot to a PVC?
description: '[Virtual Private Cloud]'
last-updated: 2026-04-30
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/containers?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Why can't I delete my File Storage for VPC snapshot to a PVC?
{: #ts-storage-vpc-file-snapshot-delete}
{: support}

[Virtual Private Cloud]{: tag-vpc}

When you try to remove your volume snapshot and volumesnapshotcontents objects, the removal fails, but your volume snapshot object shows a ReadyToUse status as false.
{: tsSymptoms}


There are finalizers preventing the resources from being removed.
{: tsCauses}


Remove the finalizers and continue deleting the resources. Note that stale `volumesnapshot` and `volumesnapshotcontents` objects can cause unnecessary `CreateSnapshot` requests, which can eventually lead to request spamming.
{: tsResolve}

* If the volumesnapshot and volumesnapshotcontent objects are included as a single mapping, follow these steps.

    1. Delete the volumesnapshot and volumesnapshotcontent objects.
        ```sh
        kubectl delete volumesnapshot snapshot-csi-file-1
        ```
        {: pre}

    1. Remove the finalizers section from the volumesnapshot resource.
        ```sh
        kubectl patch volumesnapshot/VOLUMESNAPSHOT --type json --patch='[ { "op": "remove", "path": "/metadata/finalizers" } ]'
        ```
        {: pre}

    1. Remove the finalizers section from the volumesnapshotcontents resource.
        ```sh
        kubectl patch volumesnapshotcontent/snapcontent-VOLUMESNAPSHOTCONTENT --type json --patch='[ { "op": "remove", "path": "/metadata/finalizers" } ]'
        ```
        {: pre}


* If the volumesnapshot object is deleted, but volumesnapshotcontent object still exists, complete the following steps:

    1. Find the volumesnapshotcontent object that does not have a `ReadyToUse` status as empty or false.
        ```sh
        kubectl get volumesnapshotcontents | egrep -v 'true'
        ```
        {: pre}

    1. Delete the snapshot object.
        ```sh
        kubectl delete volumesnapshotcontent snapcontent-011b11d1-1101-4b11-b1b1-011abcde11db
        ```
        {: pre}

    1. Remove the finalizer.
        ```sh
        kubectl patch volumesnapshotcontent/snapcontent-011b11d1-1101-4b11-b1b1-011abcde11db --type json --patch='[ { "op": "remove", "path": "/metadata/finalizers" } ]'
        ```
        {: pre}

    1. If the issue persists, contact support. Open a [support case](https://cloud.ibm.com/docs/support?topic=support-using-avatar&format=markdown). In the case details, be sure to include any relevant log files, error messages, or command outputs.