Skip to content

Commit 2faf198

Browse files
Merge pull request #302196 from guptasonia/patch-22
Update storage-files-how-to-mount-nfs-shares.md
2 parents 729e969 + 3a2f6bc commit 2faf198

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

articles/storage/files/storage-files-how-to-mount-nfs-shares.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -132,6 +132,7 @@ The following mount options are recommended or required when mounting NFS Azure
132132
| `noresvport` | n/a | Recommended for kernels below 5.18. Tells the NFS client to use a nonprivileged source port when communicating with an NFS server for the mount point. Using the `noresvport` mount option helps ensure that your NFS share has uninterrupted availability after a reconnection. Using this option is recommended for achieving high availability. |
133133
| `actimeo` | 30-60 | Recommended. Specifying `actimeo` sets all of `acregmin`, `acregmax`, `acdirmin`, and `acdirmax` to the same value. Using a value lower than 30 seconds can cause performance degradation because attribute caches for files and directories expire too quickly. We recommend setting `actimeo` between 30 and 60 seconds. |
134134
| `nconnect` | 4 | Recommended. Nconnect increases performance by using multiple TCP connections between the client and your NFS share. We recommend configuring the mount options with the optimal setting of nconnect=4. Currently, there are no gains beyond four channels for the Azure Files implementation of nconnect. |
135+
| `clean` | n/a | A non-TLS mount might fail if a prior TLS mount to the same server ended abruptly, leaving stale entries. To resolve this issue, remount the share using the `clean` option, which immediately clears any stale entries. This applies only for AZNFS mount. |
135136

136137
## Step 3: Validate connectivity
137138

0 commit comments

Comments
 (0)