Skip to content

Commit b8f9a8e

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into privlink-nsg
2 parents d65870d + d208ec2 commit b8f9a8e

File tree

1 file changed

+55
-13
lines changed

1 file changed

+55
-13
lines changed

articles/storage/files/files-troubleshoot-linux-nfs.md

Lines changed: 55 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,10 @@ Even if you correctly disable idmapping, it can be automatically re-enabled in s
3636
Make sure you've disabled idmapping and that nothing is re-enabling it. Then perform the following steps:
3737

3838
- Unmount the share
39-
- Disable idmapping with `# echo Y > /sys/module/nfs/parameters/nfs4_disable_idmapping`
39+
- Disable idmapping with
40+
```bash
41+
sudo echo Y > /sys/module/nfs/parameters/nfs4_disable_idmapping
42+
```
4043
- Mount the share back
4144
- If running rsync, run rsync with the "—numeric-ids" argument from a directory that doesn't have a bad dir/file name.
4245

@@ -90,39 +93,78 @@ Disable **secure transfer required** in your storage account's configuration bla
9093

9194
:::image type="content" source="media/storage-files-how-to-mount-nfs-shares/disable-secure-transfer.png" alt-text="Screenshot of storage account configuration blade, disabling secure transfer required.":::
9295

93-
### Cause 3: nfs-common package isn't installed
94-
Before running the `mount` command, install the nfs-common package.
96+
### Cause 3: nfs-utils, nfs-client or nfs-common package isn't installed
97+
Before running the `mount` command, install the nfs-utils, nfs-client or the nfs-common package.
98+
99+
To check if the NFS package is installed, run:
100+
101+
# [RHEL](#tab/RHEL)
102+
103+
Same commands on this section apply for CentOS and Oracle Linux.
104+
105+
```bash
106+
sudo rpm -qa | grep nfs-utils
107+
```
108+
# [SLES](#tab/SLES)
95109

96-
To check if the NFS package is installed, run: `rpm qa | grep nfs-utils`
110+
```bash
111+
sudo rpm -qa | grep nfs-client
112+
```
113+
# [Ubuntu](#tab/Ubuntu)
114+
115+
Same commands on this section apply for Debian.
116+
117+
```bash
118+
sudo dpkg -l | grep nfs-common
119+
```
120+
---
97121

98122
#### Solution
99123

100124
If the package isn't installed, install the package using your distro-specific command.
101125

102-
##### Ubuntu or Debian
126+
# [RHEL](#tab/RHEL)
127+
128+
Same commands on this section apply for CentOS and Oracle Linux.
103129

130+
Os Version 7.X
131+
132+
```bash
133+
sudo yum install nfs-utils
104134
```
105-
sudo apt update
106-
sudo apt install nfs-common
135+
OS Version 8.X or 9.X
136+
137+
```bash
138+
sudo dnf install nfs-utils
107139
```
108140

109-
##### Fedora, Red Hat Enterprise Linux 8+, CentOS 8+
141+
# [SLES](#tab/SLES)
110142

111-
Use the dnf package manager: `sudo dnf install nfs-utils`.
143+
```bash
144+
sudo zypper install nfs-client
145+
```
112146

113-
Older versions of Red Hat Enterprise Linux and CentOS use the yum package manager: `sudo yum install nfs-common`.
147+
# [Ubuntu](#tab/Ubuntu)
114148

115-
##### openSUSE
149+
Same commands on this section apply for Debian.
116150

117-
Use the zypper package manager: `sudo zypper install-nfscommon`.
151+
```bash
152+
sudo apt update
153+
sudo apt install nfs-common
154+
```
155+
---
118156

119157
### Cause 4: Firewall blocking port 2049
120158

121159
The NFS protocol communicates to its server over port 2049. Make sure that this port is open to the storage account (the NFS server).
122160

123161
#### Solution
124162

125-
Verify that port 2049 is open on your client by running the following command: `telnet <storageaccountnamehere>.file.core.windows.net 2049`. If the port isn't open, open it.
163+
Verify that port 2049 is open on your client by running the following command. If the port isn't open, open it.
164+
165+
```bash
166+
sudo nc -zv <storageaccountnamehere>.file.core.windows.net 2049
167+
```
126168

127169
## ls hangs for large directory enumeration on some kernels
128170

0 commit comments

Comments
 (0)