NFS: server is not responding, still trying reason and Solution

Today, I used the Development Board to mount a host through NFS and wanted to copy some information from the host. However, NFS: server is not responding, still trying, and I used the friendly mini2440, the operating system uses ubuntu8.04.
I thought it was an NFS fault, but Google found that it was not the reason for NFS, but because the transmitted data was too large, resulting in packet loss.
The default NFS transmission protocol is UDP, and serious Nic packet loss occurs when the PC interacts with the embedded system through UPD. The available solution is to switch to the TCP protocol on the client and use the following command,


Mount-T nfs-O intr, nolock, rsize = 1024, wsize = 1024 192.168.0.121:/host NFS directory/Mount path

Note: Use commas instead of periods in English.

------------------------------------------------- The following methods can also be used to solve -----------------------------------------------------------------------
In the past, NFS was transmitted over UDP by default, so when you copy a large number of files to the target board on the host, it is very likely that the packets will be lost.

Solution
Target Board: Mount-T nfs-O nolock-o tcp 192.168.1.121:/root/share/Host
In the future, copying files is generally stable.