Attempting to mount FlexCache path gives "mount.nfs: Connection timed out"

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 138

Visibility:: Public

Votes:: 0

Category:: ontap-9

Specialty:: nfs

Last Updated:

Applies to

ONTAP 9
NFSv3 / Mount protocol
FlexCache volume

Issue

"mount.nfs: Connection timed out" on Linux, or equivalent mount error (actual error logged will be client platform specific.)
When attempting to mount particular paths from a FlexCache volume, the mount operation times out.
A packet trace shows that the NULL call for mount is replied to, but the MNT call is not - the client performs RPC retransmission of its request, but does not get a response (see Wireshark / tshark output example below.)

23 0.001398 10.216.29.66 → 10.216.29.68 MOUNT V3 NULL Call 24 0.001579 10.216.29.68 → 10.216.29.66 MOUNT V3 NULL Reply (Call In 23) 25 0.001848 10.216.29.66 → 10.216.29.68 MOUNT V3 NULL Call 26 0.002001 10.216.29.68 → 10.216.29.66 MOUNT V3 NULL Reply (Call In 25) 27 0.002039 10.216.29.66 → 10.216.29.68 MOUNT V3 MNT Call /cache_vol1/qtree/link-to-dir1 29 5.016283 10.216.29.66 → 10.216.29.68 MOUNT [RPC retransmission of #27]V3 MNT Call /cache_vol1/qtree/link-to-dir1 31 15.032252 10.216.29.66 → 10.216.29.68 MOUNT [RPC retransmission of #27]V3 MNT Call /cache_vol1/qtree/link-to-dir1