Mount Target is in a Failed State

Symptom: A mount target reports a Failed state. File systems are not accessible using the mount target's IP address.

Possible Cause: There are insufficient unallocated IP addresses in the subnet. The mount target cannot fail over successfully.

Each mount target requires three internal IP addresses in the subnet to function:

  • Two of the IP addresses are used during mount target creation. The third IP address must remain available for the mount target to use for high availability failover.
  • The third IP address is used to create a new VNIC for the mount target during failover. The original primary IP address is retained.
  • The File Storage service doesn't "reserve" the third IP address required for high availability failover.
  • Use care to ensure that enough unallocated IP addresses remain available for your mount targets to use during failover.
  • Do not use /30 or smaller subnets for mount target creation because they do not have sufficient available IP addresses for mount target creation.


  1. Delete the failed mount target.

    To delete a mount target

  2. Export the file system through an active mount target. You can create a replacement mount target and then create an export for the file system, or create an export for the file system in a pre-existing mount target.

    • You can use the same export paths for the associated file systems as the previous mount target. However, the export path must be unique for each file system within the mount target.
    • If you create a replacement mount target, you can use the same IP address as the previous mount target, if available. Be sure to explicitly specify the desired IP address when you create the mount target.

    To create a mount target

    To create an export for a file system

  3. If necessary, mount the file systems again.

    Mounting File Systems


    If a replacement mount target uses exactly the same IP address and export paths as previously existed in the deleted mount target, mounted instances reconnect automatically.
  4. To prevent a recurrence of this issue, ensure that sufficient unallocated IP addresses remain available in the subnet.