Problem
When copying files larger than about 8 kilobytes (KB), the error "NFS server not responding" appears on the console; sometimes the system panics.
Cause
NFS read and write transfer sizes default to an 8KB blocksize. The above error is seen when the NFS client cannot handle this size. Usually, this indicates a faulty network adapter driver. That is, the driver is not dealing properly with full frames and back-to-back packets.
This could also be caused by a difference in the mtu (maximum transfer unit) settings on the client and server network interfaces.
Solution
This problem is usually solved by updating the network adapter driver on the client (or replacing the NIC altogether). The interface's settings (including mtu) can be seen in the output of ndstat -l and ifconfig -a.
As a troubleshooting step and temporary workaround, try mounting the NFS filesystem with a reduced buffer size. This might lower performance, but it will allow NFS transfers to complete:
mount -r -f NFS,rsize=1024,wsize=1024 remote_sys:/remote_fs /mountdirwhere "remote_sys" is the name of the server exporting the filesystem, "remote_fs" is the name of the exported filesystem, and "mountdir" is the name of the directory you are mounting to.
If the above does not help, try increasing the NFS timeout and re-transmission values:
mount -r -f NFS,timeo=1000,retrans=25 remote_sys:/remote_fs /mountdirTo mount the NFS filesystems with the options on boot, they must be added to the mntopts keyword in the file /etc/default/filesys (see filesys(F) for more information). The following is an example of such an entry reducing the read and write transfer sizes to 1KB:
bdev=nfs_svr:/remote mountdir=/remote_mnt fstyp=NFS \
fsck=no fsckflags= \
init=yes initcmd="sleep 2" \
mntopts="bg,soft,rsize=1024,wsize=1024,timeo=1000,retrans=25" \
rcmount=yes rcfsck=no
mountflags=NOTES: Check your network adapter manufacturer's web site or
https://ftp.scoexpert.com/drivers for updated NIC drivers.NOTES: If you see a "Divide by 0" or "Divide by Zero" message when
performing a "dir" from a DOS client then it is likely that the
NFS client is unable to determine the disk size capacity from the
NFS server. This may also result in a high system CPU use depending
on the NFS versions in use. See also
Manual page: mount(ADM)