From: "J. Bruce Fields" <bfields@fieldses.org>
To: jupiter <jupiter.hce@gmail.com>, NFS list <linux-nfs@vger.kernel.org>
Subject: Re: NFS 4 error
Date: Wed, 4 Sep 2013 15:38:52 -0400 [thread overview]
Message-ID: <20130904193852.GD10232@fieldses.org> (raw)
In-Reply-To: <20130904162045.GC7433@us.ibm.com>
On Wed, Sep 04, 2013 at 11:20:45AM -0500, Malahal Naineni wrote:
> jupiter [jupiter.hce@gmail.com] wrote:
> > Hi,
> >
> > I am running NFS 4 server on CentOS 6.4 for many months, it works
> > well. Recently I found that the dmesg display many following errors
> > but it still works. I searched google but could not find result of how
> > to fix it. What are those error message means? Are the errors serious
> > or not? How to fix it?
> >
> > --------
> > rpc-srv/tcp: nfsd: got error -32 when sending 24 bytes - shutting down socket
> > rpc-srv/tcp: nfsd: got error -32 when sending 24 bytes - shutting down socket
>
> When the nfsd (NFS server thread) was trying to send something, it got
> -32 (EPIPE) error. I have seen this kind of errors when the socket is
> closed by clients. Clients do close the socket (and recreate one) when
> they need to retry due to network failures.
>
> They are NOT serious errors, and if they are still happening, then look
> at your network errors/retries etc.
We should really just demote this to a dprintk, in that case.
The network failures are potentially a serious problem if they mean the
client's forced to retry a nonidempotent operation. But we probably
shouldn't be spamming the logs by default?
--b.
next prev parent reply other threads:[~2013-09-04 19:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 6:14 NFS 4 error jupiter
2013-09-04 16:20 ` Malahal Naineni
2013-09-04 19:38 ` J. Bruce Fields [this message]
2013-09-04 19:50 ` Malahal Naineni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130904193852.GD10232@fieldses.org \
--to=bfields@fieldses.org \
--cc=jupiter.hce@gmail.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.