Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
On this page

Mounting an NFS File System to ECSs (Linux)

Updated on 2022-08-16 GMT+08:00

After creating a file system, you need to mount the file system to ECSs so that they can share the file system.

Operations on BMSs are the same as those on ECSs.

Prerequisites

  • You have checked the type of the operating system on each ECS. Different operating systems use different commands to install the NFS client.
  • You have created a file system and have obtained the mount point of the file system.
  • At least one ECS that belongs to the same VPC as the file system exists.

Procedure

  1. Log in to the management console using a cloud account.

    1. Log in to the management console and select a region and a project.
    2. Under Computing, click Elastic Cloud Server to switch to the ECS console.

  2. Log in to the ECS as user root.

    NOTE:

    If you log in to the ECS as a non-root user, see Mounting a File System to an ECS Running Linux as a Non-root User.

  3. Install the NFS client.

    1. Run the following command to check whether the NFS software package is installed.
      • On CentOS, Red Hat, Oracle Enterprise Linux, SUSE, EulerOS, Fedora, or OpenSUSE:

        rpm -qa|grep nfs

      • On Debian or Ubuntu:

        dpkg -l nfs-common

      If nothing is displayed, go to 3.b.
      • On CentOS, Red Hat, EulerOS, Fedora, or Oracle Enterprise Linux:
        libnfsidmap
        nfs-utils
      • On SUSE or OpenSUSE:
        nfsidmap
        nfs-client
      • On Debian or Ubuntu:
        nfs-common
    2. Run the following command to install the NFS software package.
      NOTE:

      The following commands require that ECSs be connected to the Internet. Otherwise, the installation will fail.

      • On CentOS, Red Hat, EulerOS, Fedora, or Oracle Enterprise Linux:

        sudo yum -y install nfs-utils

      • On Debian or Ubuntu:

        sudo apt-get install nfs-common

      • On SUSE or OpenSUSE:

        zypper install nfs-client

  4. Run the following command to create a local path for mounting the file system:

    mkdir Local path

    NOTE:

    If there are resources, such as disks, already mounted on the local path, create a new path.

  5. Run the following command to mount the file system to the ECS that belongs to the same VPC as the file system. Currently, the file system can be mounted to the ECS running Linux using NFSv3 only.

    Table 1 describes the variables.

    To mount an SFS Turbo file system, run the following command: mount -t nfs -o vers=3,timeo=600,noresvport,nolock Mount point Local path

    NOTICE:

    After an ECS where file systems have been mounted restarts, it loses the file system mount information. You can configure automatic mount in the fstab file to ensure that an ECS automatically mounts file systems when it restarts. For details, see Mounting a File System Automatically.

    Table 1 Parameter description

    Parameter

    Description

    vers

    File system version. Only NFSv3 is supported currently, so the value is fixed to 3.

    timeo

    Waiting time before the NFS client retransmits a request. The unit is 0.1 second. The recommended value is 600.

    resvport/noresvport

    Whether the confidential source port is used for server connection. By default, resvport indicates that the confidential port is used, and noresvport indicates that the confidential port is not used. The kernel version is 2.6.28 or later.

    You are advised to set this parameter to noresvport so that a new TCP port can be used when the network is reconnected. This ensures that the connection is not interrupted when the network recovers from a fault.

    lock/nolock

    Whether to lock files on the server using the NLM protocol. If nolock is selected, the lock is valid for applications on one host. For applications on another host, the lock is invalid. The recommended value is nolock. If this parameter is not specified, lock is selected by default. In this case, other servers cannot write data to the file system.

    Mount point

    The format for an SFS Turbo file system is File system IP address:/, for example, 192.168.0.0:/.

    Local path

    Local path on the ECS, used to mount the file system, for example, /local_path.

    For more mounting parameters for performance optimization during file system mounting, see Table 2. Use commas (,) to separate parameters. The following command is an example:

    mount -t nfs -o vers=3,timeo=600,nolock,rsize=1048576,wsize=1048576,hard,retrans=3,noresvport,async,noatime,nodiratime Mount point Local path

    Table 2 Parameters for file system mounting

    Parameter

    Description

    rsize

    Maximum number of bytes that can be read from the server each time. The actual data is less than or equal to the value of this parameter. The value of rsize must be a positive integer that is a multiple of 1024. If the entered value is smaller than 1024, the value is automatically set to 4096. If the entered value is greater than 1048576, the value is automatically set to 1048576. By default, the setting is performed after the negotiation between the server and the client.

    You are advised to set this parameter to the maximum value 1048576.

    wsize

    Maximum number of bytes that can be written to the server each time. The actual data is less than or equal to the value of this parameter. The value of wsize must be a positive integer that is a multiple of 1024. If the entered value is smaller than 1024, the value is automatically set to 4096. If the entered value is greater than 1048576, the value is automatically set to 1048576. By default, the setting is performed after the negotiation between the server and the client.

    You are advised to set this parameter to the maximum value 1048576.

    soft/hard

    soft indicates that a file system is mounted in soft mount mode. In this mode, if an NFS request times out, the client returns an error to the invoking program. hard indicates that a file system is mounted in hard mount mode. In this mode, if the NFS request times out, the client continues to request until the request is successful.

    The default value is hard.

    retrans

    Number of retransmission times before the client returns an error. The default value is 3.

    resvport/noresvport

    Whether the confidential source port is used for server connection. By default, resvport indicates that the confidential port is used, and noresvport indicates that the confidential port is not used. The kernel version is 2.6.28 or later.

    You are advised to set this parameter to noresvport so that a new TCP port can be used when the network is reconnected. This ensures that the connection is not interrupted when the network recovers from a fault.

    sync/async

    sync indicates that data is written to the server immediately. async indicates that data is first written to the cache before being written to the server.

    Synchronous write requires that an NFS server returns a success message only after all data is written to the server, which brings long latency. The recommended value is async.

    noatime

    If you do not need to record the file access time, set this parameter. This prevents overheads caused by access time modification during frequent access.

    nodiratime

    If you do not need to record the directory access time, set this parameter. This prevents overheads caused by access time modification during frequent access.

    NOTE:

    You are advised to use the default values for the parameters without usage recommendations.

  6. Run the following command to view the mounted file system:

    mount -l

    If the command output contains the following information, the file system is mounted successfully.
    Mount point on /local_path type nfs (rw,vers=3,timeo=600,nolock,addr=)

  7. After the file system is mounted successfully, access the file system on the ECSs to read or write data.

    If the mounting fails or times out, rectify the fault by referring to Troubleshooting.

    NOTE:

    The maximum size of a file that can be written to an SFS Turbo file system is 16 TB.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback