You are troubleshooting the failure of a computer to mount an NFS file system hosted by a server (hostname mars) in the local area network. Select the three commands that will enable you to identify…

Question

Options

• Aping - s mars
• Bcat /etc/vfstab
• Ccat /etc/dfs/dfstab
• Dsharemgr show -v
• Eshowmount -e mars
• Frpcinfo -s mars | egrep `nfs|mountd'

• A
  63% (12)
• B
  11% (2)
• C
  21% (4)
• D
  5% (1)

Explanation

Troubleshooting an NFS mount failure requires verifying three things from the client side: network reachability, server exports, and RPC service availability. ping -s mars (A) confirms basic connectivity - if the server is unreachable, nothing else matters. showmount -e mars (E) queries the server remotely to verify it is actually exporting the expected filesystem. rpcinfo -s mars | egrep 'nfs|mountd' (F) confirms the NFS daemon and mount daemon are registered and running on the server via RPC - both must be active for a mount to succeed.

The distractors fail because they don't diagnose the remote server from the client. cat /etc/vfstab (B) only shows the client's local mount configuration - useful for checking syntax, but it can't reveal why the server is unresponsive. cat /etc/dfs/dfstab (C) and sharemgr show -v (D) both deal with share configuration on the local machine; running them on the client tells you nothing about what mars is sharing.

Memory tip: Think of the three diagnostic layers as "Can I find it? Can I see it? Can I talk to it?" - ping = find the host, showmount = see its exports, rpcinfo = talk to its NFS services. All three must succeed for an NFS mount to work.

No community discussion yet for this question.