Azure NetApp Files
An Azure service that provides enterprise-grade file shares powered by NetApp.
NFS not responding and mounts un-resposive.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(236.8, 82%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESL%3C/text%3E%3C/svg%3E)
Srikanth L
90
Reputation points Microsoft Employee
Hi,
We are seeing the “NFS not responding” error message on client machines for the following volumes:
172.20.126.110:/eus-aisieshared-diamondlake-prod
172.20.126.112:/eus-aisiepd-3rd-party-prod
172.20.126.111:/eus-aisieshared-kendall-prod
this error appears on the client machines (unix), I would like to have detailed debugging performed on the storage side to check for any network path or performance issues, or any other underlying cause. At times, we also observe that the mounts become unresponsive or hung.
This issue is happening randomly for last three days. Let me know if any other details required on the same.
Azure NetApp Files
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 22%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETG%3C/text%3E%3C/svg%3E)
Thanmayi Godithi 10,115 Reputation points Microsoft External Staff Moderator2026-05-20T10:58:50.1966667+00:00 Hi Srikanth L ,
Based on the behaviour (“NFS not responding” and hung mounts), this usually indicates intermittent connectivity or backend response issues.
Could you please help check the below:
- Basic connectivity:
Check for packet loss or high latencyping <NFS-IP> - Please run
showmount -e <NFS-IP>from one of the affected Unix client machines.This should respond quickly — if it hangs, it points to network/storage issue - Have there been any recent changes to NSG rules, firewall, routing (UDR), or network configuration in the last few days?
- Which NFS version is currently in use (v3 or v4.1), and what mount options are configured?
This will help quickly identify whether the issue is network-related or on the storage side.
Thanks.
- Basic connectivity:
-
Srikanth L 90 Reputation points Microsoft Employee
2026-05-21T00:24:58.13+00:00 please increase the priority of the case.
As suggested tried this from impacted host.
Showmount -e <IP address> returning the NFS mount
please find the ping response below.
PING 172.20.126.110 (172.20.126.110) 56(84) bytes of data.
64 bytes from 172.20.126.110: icmp_seq=1 ttl=63 time=1.15 ms
64 bytes from 172.20.126.110: icmp_seq=2 ttl=63 time=1.13 ms
64 bytes from 172.20.126.110: icmp_seq=3 ttl=63 time=1.10 ms
64 bytes from 172.20.126.110: icmp_seq=4 ttl=63 time=1.12 ms
64 bytes from 172.20.126.110: icmp_seq=5 ttl=63 time=1.10 ms
64 bytes from 172.20.126.110: icmp_seq=6 ttl=63 time=0.819 ms
64 bytes from 172.20.126.110: icmp_seq=7 ttl=63 time=1.03 ms
64 bytes from 172.20.126.110: icmp_seq=8 ttl=63 time=0.888 ms
64 bytes from 172.20.126.110: icmp_seq=9 ttl=63 time=1.17 ms
64 bytes from 172.20.126.110: icmp_seq=10 ttl=63 time=0.898 ms
64 bytes from 172.20.126.110: icmp_seq=11 ttl=63 time=0.801 ms
64 bytes from 172.20.126.110: icmp_seq=12 ttl=63 time=1.04 ms
64 bytes from 172.20.126.110: icmp_seq=13 ttl=63 time=0.877 ms
64 bytes from 172.20.126.110: icmp_seq=14 ttl=63 time=0.785 ms
64 bytes from 172.20.126.110: icmp_seq=15 ttl=63 time=0.868 ms
64 bytes from 172.20.126.110: icmp_seq=16 ttl=63 time=0.903 ms
64 bytes from 172.20.126.110: icmp_seq=17 ttl=63 time=0.835 ms
64 bytes from 172.20.126.110: icmp_seq=18 ttl=63 time=0.923 ms
64 bytes from 172.20.126.110: icmp_seq=19 ttl=63 time=1.14 ms
64 bytes from 172.20.126.110: icmp_seq=20 ttl=63 time=1.07 ms
64 bytes from 172.20.126.110: icmp_seq=21 ttl=63 time=1.09 ms
64 bytes from 172.20.126.110: icmp_seq=22 ttl=63 time=0.950 ms
64 bytes from 172.20.126.110: icmp_seq=23 ttl=63 time=0.983 ms
64 bytes from 172.20.126.110: icmp_seq=24 ttl=63 time=1.11 ms
64 bytes from 172.20.126.110: icmp_seq=25 ttl=63 time=0.898 ms
64 bytes from 172.20.126.110: icmp_seq=26 ttl=63 time=1.10 ms
64 bytes from 172.20.126.110: icmp_seq=27 ttl=63 time=1.06 ms
64 bytes from 172.20.126.110: icmp_seq=28 ttl=63 time=0.937 ms
64 bytes from 172.20.126.110: icmp_seq=29 ttl=63 time=1.10 ms
64 bytes from 172.20.126.110: icmp_seq=30 ttl=63 time=0.952 ms
64 bytes from 172.20.126.110: icmp_seq=31 ttl=63 time=1.00 ms
64 bytes from 172.20.126.110: icmp_seq=32 ttl=63 time=0.942 ms
64 bytes from 172.20.126.110: icmp_seq=33 ttl=63 time=1.11 ms
64 bytes from 172.20.126.110: icmp_seq=34 ttl=63 time=1.03 ms
64 bytes from 172.20.126.110: icmp_seq=35 ttl=63 time=1.09 ms
64 bytes from 172.20.126.110: icmp_seq=36 ttl=63 time=0.969 ms
64 bytes from 172.20.126.110: icmp_seq=37 ttl=63 time=1.05 ms
64 bytes from 172.20.126.110: icmp_seq=38 ttl=63 time=1.09 ms
64 bytes from 172.20.126.110: icmp_seq=39 ttl=63 time=0.968 ms
64 bytes from 172.20.126.110: icmp_seq=40 ttl=63 time=1.14 ms
-
Thanmayi Godithi 10,115 Reputation points Microsoft External Staff Moderator
2026-05-21T03:53:37.6266667+00:00 Hi Srikanth L ,
Thank you for providing the details.
I will check and will reach out to you on Teams shortly.
Sign in to comment
Sign in to answer