NFS read failed for server string

Cause
This message generally indicates a permissions problem. Perhaps a directory or file
permission was changed while the client kept the file open. Perhaps the file system’s
share or netgroup permissions changed. If the server were down or the network
overloaded, the NFS server not responding message would appear instead.
Action
Log in to the NFS server and check the permissions of directories leading to the file.
Make certain that the file system is shared with (exported to) the client experiencing
an NFS read failure.

nfs_server: bad getargs for int/int

Cause
This message comes from the NFS server when it receives a request with
unrecognized or incorrect arguments. Typically, it means the request could not be
XDR decoded properly. This error can result from corruption of the packet over the
network, or from an implementation bug causing the NFS client to encode its
arguments improperly.
Action
If this message originates from a single client, investigate that machine for NFS client
software bugs. If this message appears throughout a network, especially accompanied
by other networking errors, investigate the network cabling and connectors.

NFS server string not responding still trying

Cause
In most cases this common message indicates that the system has requested a service
from an NFS server that is either down or extremely slow to respond. In some cases
this message indicates that the network link to this NFS server is broken, although
usually that condition generates other error messages as well. In a few cases this
message indicates NFS client setup problems.
Action
Check the non-responding NFS server for the need for machine repair or rebooting.
Encourage your user community to report such problems quickly but only once.

NFS server string ok

Cause
This message is the follow-up to the NFS server not responding error. It
indicates that the NFS server is again operating.
Action
When an NFS server first starts, it is busy fulfilling client requests for a while. Be
patient and wait for your client system to respond. Making many extraneous
requests only further slows the NFS server response time.

nfs umount: string: is busy

Cause
This message appears when the superuser attempts to unmount an active NFS file
system. The busy point is the working directory of a process.
Action
Determine which shell (or process) on the workstation is currently located in the
remotely mounted file system, and change— cd(1)—out of that directory. Be wary of
subshells (such as su(1M) shells) that could be in different directories while the
parent shells remain in the NFS file system.

NFS write error on host string: No space left on

device.

Cause
This console message indicates that an NFS-mounted partition has filled up and
cannot accept writing of new data. Unfortunately, software that attempts to
overwrite existing files will usually zero-out all data in these files. This is particularly
destructive on NFS-mounted /home partitions.

Action
Find the user or process that is filling up the file system, and stop the out-of-control
process as soon as you can. Then delete files as necessary to create more space on the
file system (large core(4) files are good candidates for deletion). Have users write
any modified files to local disk if possible. If this error occurs often, redistribute
directories to ease the demand on this partition.

NFS write failed for server string: RPC: Timed out

Cause
This error can occur when a file system is soft mounted, and server or network
response time lags. Any data written to the server during this period could be
corrupted.
Action
If you intend to write on a file system, never specify the soft-mount option. Use the
default hard mount for all the file systems that are mounted read-write.