string
string
string
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
NFS read failed for server <strong>string</strong><br />
Cause<br />
This is generally a permissions problem. Perhaps a directory or file permission was<br />
changed while the client held the file open. Perhaps the filesystem’s share or<br />
netgroup permissions changed. If the server were down or the network saturated,<br />
the "NFS server not responding" message would appear instead.<br />
Action<br />
Log in to the NFS server and check the permissions of directories leading to the file.<br />
Make certain that the filesystem is shared with (exported to) the client experiencing<br />
an NFS read failure.<br />
See Also<br />
For more information, see the chapter on NFS troubleshooting in the NFS<br />
Administration Guide.<br />
nfs_server: bad getargs for int/int<br />
Cause<br />
This message comes from the NFS server when it recieves a request with<br />
unrecognized or incorrect arguments. Typically, it means the request could not be<br />
XDR decoded properly. This can result from corruption of the packet over the<br />
network, or from an implementation bug causing the NFS client to improperly<br />
encode its arguments.<br />
Action<br />
If this message originates from a single client, investigate that machine for NFS client<br />
software bugs. If this message appears throughout a network, especially accompanied<br />
by other networking errors, investigate the network cabling and connectors.<br />
124 Solaris Common Messages and Troubleshooting Guide ♦ October, 1998
Change language