After you create an Apsara File Storage NAS (NAS) file system, you must mount the file system as a directory on one or more compute nodes to enable shared access. NAS supports shared access with compute nodes of the following services: Elastic Compute Service (ECS), Container Service for Kubernetes (ACK), Function Compute, and Platform For AI (PAI). This topic describes the precautions and scenarios for mounting NAS file systems. Read this topic before you mount a NAS file system.
If you have any feedback or questions, contact NAS technical support by clicking the button below.
Precautions
Before you mount a file system, you must Create a file system and Create a mount target.
You can mount a NAS file system only on a compute node that resides in the same virtual private cloud (VPC) as the mount target of the file system. The private IP address of the compute node must be authorized in a rule of the permission group that is attached to the mount target. For more information, see Manage permission groups.
NoteOn and after November 21, 2022, classic network mount targets cannot be created for General-purpose NAS file systems. However, classic network mount targets created before November 21, 2022 can still be used to access file systems.
If a mount target resides in the classic network, only the ECS instances in the classic network can access the mount target. The private IP address of the ECS instance must be authorized in a rule of the permission group that is attached to the mount target. You can migrate an ECS instance from the classic network to a VPC. For more information, see Migrate ECS instances from the classic network to a VPC.
You can mount a General-purpose NAS file system across multiple zones. We recommend that you mount an Extreme NAS file system on an ECS instance that resides in the same zone as the file system. Otherwise, the performance of the Extreme NAS file system is degraded.
Extreme NAS file systems support only Linux operating systems and can be accessed by using only NFSv3.
To ensure compatibility and stability, we recommend that you use Network File System (NFS) file systems on Linux and Server Message Block (SMB) file systems on Windows. To prevent compatibility issues that may affect system stability, we recommend that you do not mount an SMB file system on Linux or mount an NFS file system on Windows. For more information about the compatibility issues that may occur when you mount a file system across platforms, see FAQ about read and write access to files.
Scenarios
Mount NAS file systems on ECS instances
Use the NAS console to mount file systems
Run the mount command to mount a file system
If you are unable to mount a file system on an ECS instance, you can use the scripts that are provided by NAS to troubleshoot issues. For more information, see FAQ about troubleshooting of mount failures.
Mount NAS file systems on containers
To mount a file system on a container, use the methods described in Recommended mount methods.
You can mount NAS file systems on ACK clusters, ACK Serverless clusters, and self-managed Kubernetes clusters. For more information, see the following topics:
Mount a file system on a Function Compute function
You can mount a file system on a Function Compute function. For more information, see the following topics:
Mount a file system on a Function Compute function
Mount file systems on PAI
NAS is seamlessly integrated with PAI. You can configure a NAS file system as a dataset to persistently store data during deployment and training. For more information, see Getting started (PAI-DSW).
Mount a file system across VPCs, regions, and accounts
You can use PrivateLink or Cloud Enterprise Network (CEN) to mount a file system across VPCs in the same region, or across different accounts and regions.
Mount a NAS file system across VPCs in the same region
Mount a NAS file system across accounts and regions
Use CEN to mount a NAS file system across accounts and regions
Access a file system from a data center
If a server in your on-premises data center needs to access a NAS file system, you can use one of the following methods to mount the file system:
References
Data migration
Migrate data from an on-premises storage system to a NAS file system
You can migrate data from an on-premises storage system to a NAS file system by using an SFTP client, the rsync tool, or the Robocopy tool. For more information, see Migrate data from an on-premises storage system to NAS.
Migrate data from a NAS file system to an on-premises storage system
You can migrate data from a NAS file system to an on-premises storage system by using an SFTP client, the rsync tool, or the Robocopy tool. You can also synchronize data to Object Storage Service (OSS) and then download the data from OSS to local files. For more information, see Migrate data from a NAS file system to an on-premises storage system.
Unmount a file system
The following topics describe how to unmount a file system from an ECS instance: