Releases Notes and Announcements

Release Notes

Announcements

Product Introduction

Overview

Strengths

Storage Classes and Performance

Use Cases

Recommended Regions

Use Limits

Service Regions and Service Providers

Purchase Guide

Billing Overview

Pricing Overview

General Series Billing

Turbo Series Billing

High-Throughput CFS Billing

Billing Mode

IA ‍Storage Billing

Storage Resource Units

Resource Purchase

Viewing Bills

Arrears Reminder

Getting Started

Creating File Systems and Mount Targets

Use the CFS File System on a Linux Client

Using the CFS File Systems on Windows Clients

Using CFS Turbo on Linux Clients

Using the Console or CFS Client Assistant to Mount File Systems

Operation Guide

Access Management

Managing File Systems

Permission Management

Using Tags

Turbo file system metadata type

Snapshot Management

Guide for Cross-AZ and Cross-Network Access

Automatically Mounting File Systems

Data Migration Service

User Permission Management

User Quotas

Data Encryption

Data Lifecycle Management

Upgrading Standard File Systems

Practical Tutorial

NFS Client Mount Parameter Description

Selecting Kernels for NFS Clients

Managing Turbo CFS Directories

Terminating Compute Instances

Using CFS on TKE

Using CFS on SCF

Using CFS Turbo on TKE

Using CFS Turbo on TKE Serverless Cluster

Selecting a Network for Turbo CFS

Copying Data

CFS Storage Performance Testing

API Documentation

History

Introduction

API Category

Snapshot APIs

File system APIs

Lifecycle APIs

Other APIs

Data Flow APIs

Making API Requests

Permission Group APIs

Service APIs

Scaling APIs

Data Migration APIs

Data Types

Error Codes

Troubleshooting

Client Use Bottleneck due to Large Number of Small Files or Parallel Requests

FAQs

CFS Service Level Agreement

Glossary

NFS Client Mount Parameter Description

PDF

Mode fokus

Ukuran font

Terakhir diperbarui: 2026-04-08 15:13:54

This article describes common NFS client mount options to help you better understand different NFS mount option parameters and applicable scenarios. This document focuses on describing the meaning of the parameters and parameters that may require additional adjustments to meet access requirements in specific scenarios.
Note:
On the file system mount parameters page and the client assistant interface, Tencent Cloud recommended mount parameters have been provided. You can perform the mount operation based on the recommended configuration.
Description of Common Mount Parameters
Parameter
Parameter Description
vers
Indicates the version of the NFS protocol used.
3: indicates that NFS version 3 is used for mounting.
4.0: indicates that NFS version 4 is used for mounting.
Note:
It is recommended to pass vers=3 to use the NFS V3 protocol to obtain better metadata performance. If multiple clients need to edit the same file, vers=4/ can be passed.
hard/soft
hard: When CFS is unavailable, the client will automatically retry.
soft: When CFS is unavailable, the client will directly return an EIO error.
Note:
This parameter defaults to hard.
It is recommended to use the default configuration. When a primary/secondary switchover occurs in the CFS backend, the client can automatically reconnect to ensure service availability.
noresvport
Using a new TCP port during network reconnection ensures that the connection is not interrupted when network failure recovery occurs.
Note:
It is recommended to configure this. When a primary/secondary switchover occurs in the CFS backend, internal ports are replaced. This parameter must be added to ensure normal service recovery after the switchover.
ac/noac
ac: metadata information of cached files.
noac: does not cache file metadata.
Note:
This parameter defaults to ac.
It is recommended to use the default configuration for better performance.
If high consistency level is required for multi-client data reading, which is common in various workflow scenarios, it can be set to noac.
sync
After configuration, data writes will switch to synchronous writes.
Note:
It is recommended not to add this parameter to ensure better performance. If a high consistency level is required, which is common in various workflow scenarios, this parameter can be configured.
lock/nolock
nolock: switches file locking semantics to local lock without throwing errors.
lock: enable file lock semantics. If the server does not support file locks, the lock request will throw an error.
Note:
Defaults to lock. It is recommended to configure nolock when you mount with the NFS V3 protocol to ensure file locks function properly when invoked by the application.
Note:
For a more complete set of NFS client mount parameters, please refer to the official link MAN NFS.

Bantuan dan Dukungan

Apakah halaman ini membantu?

Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.

masukan

tencent cloud

Cloud File Storage

NFS Client Mount Parameter Description

Description of Common Mount Parameters

Bantuan dan Dukungan

Parameter	Parameter Description
vers	Indicates the version of the NFS protocol used. 3: indicates that NFS version 3 is used for mounting. 4.0: indicates that NFS version 4 is used for mounting. Note: It is recommended to pass vers=3 to use the NFS V3 protocol to obtain better metadata performance. If multiple clients need to edit the same file, vers=4/ can be passed.
hard/soft	hard: When CFS is unavailable, the client will automatically retry. soft: When CFS is unavailable, the client will directly return an EIO error. Note: This parameter defaults to hard. It is recommended to use the default configuration. When a primary/secondary switchover occurs in the CFS backend, the client can automatically reconnect to ensure service availability.
noresvport	Using a new TCP port during network reconnection ensures that the connection is not interrupted when network failure recovery occurs. Note: It is recommended to configure this. When a primary/secondary switchover occurs in the CFS backend, internal ports are replaced. This parameter must be added to ensure normal service recovery after the switchover.
ac/noac	ac: metadata information of cached files. noac: does not cache file metadata. Note: This parameter defaults to ac. It is recommended to use the default configuration for better performance. If high consistency level is required for multi-client data reading, which is common in various workflow scenarios, it can be set to noac.
sync	After configuration, data writes will switch to synchronous writes. Note: It is recommended not to add this parameter to ensure better performance. If a high consistency level is required, which is common in various workflow scenarios, this parameter can be configured.
lock/nolock	nolock: switches file locking semantics to local lock without throwing errors. lock: enable file lock semantics. If the server does not support file locks, the lock request will throw an error. Note: Defaults to lock. It is recommended to configure nolock when you mount with the NFS V3 protocol to ensure file locks function properly when invoked by the application.