Oracle Cloud Infrastructure Documentation

Cannot Delete VCN- Mount Target VNIC Still Attached

What is an "orphan" mount target?

An "orphan" mount target is defined as a mount target that is not associated with any file system.

How do orphan mount targets happen?

  • Using the Command Line Interface (CLI), API, Console, or a combination of these tools to delete all of a mount target's associated file systems.
  • Using the CLI, API, Console, or a combination of these tools to detach all file systems from a mount target.

Tip

Unassociated mount targets aren't always a problem unless they're overlooked. This is more likely to happen if you have multiple administrators using different tools to work with File Storage, or if you're unfamiliar with how file systems, mount targets, subnets, and VCNs are related.

What problems can they cause?

Unassociated, "orphan" mount targets that remain in your system can cause issues such as:

  • They can prevent you from deleting a VCN. Each mount target has a VNIC to enable network access. Mount target VNICs that remain in a VCN must be deleted before you can delete the VCN.
  • They can prevent you from creating new mount targets. Orphan mount targets can cause you to exceed your limit without realizing it. However, any mount target can be associated with up to 100 file systems, so you don't always need to create a new mount target. See To add a mount target to a file system for more information.
  • See Service Limits for a list of applicable limits and instructions for requesting a limit increase.

How can I tell if I have orphan mount targets?

To identify orphan mount targets in the Console
To identify orphan mount targets using the API
To identify orphan mount targets using the CLI

What should I do with an orphan mount target?

You can:

Deleting unassociated ("orphan") mount targets

To delete orphan mount targets in the Console
To delete orphan mount targets in the API
To delete orphan mount targets in the CLI