On Fri, 2008-04-04 at 15:33 -0400, Talpey, Thomas wrote: > If it fails with a server-provided error such as this, the caller can and > should decide what to do - if that caller is NFS, it can apply soft/hard > to the retry decision. But Chuck's example, for instance, is NFSD. Note that ECONNREFUSED doesn't necessarily mean that the service is down; it may also indicate a SYN backlog. In most cases, you therefore definitely want to try to handle this type of error in the RPC layer, not the caller. If you fault back to the caller, then you lose RPC level information, and in particular, you will lose the XID. If you were trying to reconnect in order to replay the RPC request, then that can be a real problem... -- Trond Myklebust Linux NFS client maintainer NetApp Trond.Myklebust@xxxxxxxxxx www.netapp.com -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
