Re: nfs client error w/2.1.76
kwrohrer@enteract.com
Wed, 31 Dec 1997 13:56:25 -0600 (CST)
And lo, Bill Hawes saith unto me:
> kwrohrer@enteract.com wrote:
> > As I was rebooting my NFS server, I got plenty of:
> >
> > nfs_revalidate_inode: getattr failed, error=-111
> > nfs: RPC call returned error 111
> > RPC: task of released request still queued!
> > RPC: (task is on xprt_pending)
>
> Error 111 is "connection refused", so this is probably normal while
> rebooting the server. Did the client work OK after the server was up
> again?
It comes back fine. However, the amount of messages in the log for
connection refused is much higher than in the case of ripped-out-cable
or kswapd-won't-give-adequate-size-hunks-of-RAM-for-the-ip-fragment-
buffer-to-grow.
And it was the RPC: apparent errors which worried me. These should be
labeled as warnings or fixed.
Keith (a 1.7G partition takes a while to fsck with only 24M)