NFS: server is not responding, still trying !! Cause and Solution

Method 1:
The following error message is displayed when I share files through NFS on the arm.
NFS: server is not responding, still trying
Cause analysis: the default NFS transmission protocol is UDP, and serious Nic packet loss occurs when the PC interacts with the embedded system through UPD.
Solution: switch to the TCP protocol on the client and use the following command,
# Mount-o tcp 10.10.19.25:/home/export/mnt/local
Method 2:
Problems encountered when copying large files on the PC to the target board through NFS on the target board:
NFS: Server *** not responding, still trying
Modification method:
NFS crashes during NFS mount. Mount the NFS as follows:
Mount-T nfs-O intr, nolock, rsize = 1024, wsize = 1024 192.168.1.3/root/somedir/client
Cause:
Mandag 27 November 2006 skrev Verner kJ? Rsgaard:
> Mandag 27 November 2006 skrev John P. New:
> Verner,
>
> This is a problem with NFS and 2.6 kernels, fast server networking and
> Comparatively slower client startup. This will show up when the server has
> A 1000 MB card and the client a 100 MB, or when the server has a 100 MB
> Card and the client a 10 MB.
>
> Essential, you have to pass some options to the kernel on Terminal
> Boot, and this varies depending on whether you are using etherboot or
> PXE.
>
> See
> Http://wiki.ltsp.org/twiki/bin/view/Ltsp/NFS#NFS_Server_not_responding
> For a deeper explanation of the problem and the cure.
// Note: The cause is that the NIC transmission rate of the server and the target machine conflicts, so that the target machine needs a lot of time to copy a large number of data packets. In fact, if the NIC speed of the target machine is large enough, it does not need to be divided into so many packets, nor conflict.
Appendix 4: During the test, "./progressbar-qws" prompts the same as Q3, which should be handled by Q3.
The above references some "happy sky" experiences. His webpage is:
Http://blog.chinaunix.net/u2/67519/showart_677885.html
His
Mount-T nfs-O intr, nolock, rsize = 1024, wsize = 1024 192.168.1.3/root/somedir/Host
Should be changed
Mount-T nfs-O intr, nolock, rsize = 1024, wsize = 1024 192.168.1.3/root/somedir/client