Mount target creation can fail for various reasons:
You've exceeded your mount target limit.
Each availability domain is limited to two mount targets by default. If you create both a file system and a mount target at the same time, it is possible for the file system to be successfully created but the mount target creation to fail because of this limitation.
You can associate the new file system with a previously created mount target. For more information, see To add a mount target to a file system.
See Service Limits for a list of applicable limits and instructions for requesting a limit increase.
You have unassociated ("orphan") mount targets that have been overlooked, and they've caused you to exceed your mount target limit.
See To delete unassociated mount targets for more information.
- There aren't enough available IP addresses in your subnet.
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.
Do not use /30 or smaller subnets for mount target creation because they do not have sufficient available IP addresses for mount target creation.
The File Storage service doesn't "reserve" the third IP address required for high availability failover, so use care when designing your subnets and file systems to ensure that sufficient IP addresses remain available for your mount targets in the future.