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. |
フィードバック