Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
what is badxids in nfsstat -c
- Thread starter mingx98
- Start date
sureshp
Programmer
- Aug 28, 2000
- 79
Hi ming,
I am not sure about the badxid's. Have you gone through the man pages.
badxid's are the number of times "a reply from the server is received by the client " but the reply(s) are irrelevent to the request made by the client.
Suppose you are requesting a "file handle" from the NFS server , and you are getting reply from the server which is unappropriate to your request. These cases are counted in badxid's.
Hope I am in your line...
Suresh.
I am not sure about the badxid's. Have you gone through the man pages.
badxid's are the number of times "a reply from the server is received by the client " but the reply(s) are irrelevent to the request made by the client.
Suppose you are requesting a "file handle" from the NFS server , and you are getting reply from the server which is unappropriate to your request. These cases are counted in badxid's.
Hope I am in your line...
Suresh.
cfsalmeida
IS-IT--Management
The retrans field (under Client rpc) indicates the number of packets that this host had to retransmit as an RPC client: that is, the number of retransmissions it made while reading or writing an NFS file. If this field is greater than 5 percent of the total number of client NFS
calls, suspect trouble. Compare the number of retransmissions to the badxid field (number of times a reply from a server was received which did not correspond to any outstanding call). If badxid and retrans are roughly equal, one or more of the network's NFS servers is having trouble keeping up with the client's demands. This isn't a data corruption problem, but a performance
problem on the part of the server. If retrans is high but badxid is relatively small or zero, the problem is in the network itself - the network is either slow or suffering from data corruption.
Regards,
CA,
calls, suspect trouble. Compare the number of retransmissions to the badxid field (number of times a reply from a server was received which did not correspond to any outstanding call). If badxid and retrans are roughly equal, one or more of the network's NFS servers is having trouble keeping up with the client's demands. This isn't a data corruption problem, but a performance
problem on the part of the server. If retrans is high but badxid is relatively small or zero, the problem is in the network itself - the network is either slow or suffering from data corruption.
Regards,
CA,
- Status