From: Johan van den Dorpe <johan.vandendorpe@framestore-cfc.com>
To: linux-kernel@vger.kernel.org
Subject: nfsd: terminating on error 104 problem
Date: Wed, 25 Feb 2004 16:55:45 +0000 [thread overview]
Message-ID: <403CD391.1010809@framestore-cfc.com> (raw)
Hi all
We are currently using quite a number of HP DL380 servers within our
company that use the 2.4.25 kernel. These are primarily used for heavy
NFS access, so we keep a large number of nfsd processes concurrently
running. We have noticed over time however that nfsd processes
periodically die. From inspection of the system logs, we get numerous
entries:
Feb 22 12:25:24 ps29 kernel: nfsd: recvfrom returned errno 104
Feb 22 12:25:24 ps29 kernel: nfsd: terminating on error 104
At the moment we cron a script that counts the number of nfsds and
restart rpc.nfsd if they drop below a threshold. Although this is a
working solution, it's not ideal and we would really like to get his
problem patched up properly.
So from my limited knowledge of the kernel source I can see that
"terminating on error 104" corresponds to line 221 of
/usr/src/linux-2.4.25/fs/nfsd/nfssvc.c. So svc_recv on line 191 is
obviously returning -104.
I've noticed that in the 2.6.0 kernel there are quite a few changes to
nfssvc.c, and I wondered if they dealt with this situation.
In the mean time, are there any quick hacks I could add to nfssvc.c to
make it tolerate error -104? Could I safely alter the main request loop
to simply continue execution if svc_recv returns this code?
Any help would be much appreciated.
many thanks
--
Johan van den Dorpe
next reply other threads:[~2004-02-25 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 16:55 Johan van den Dorpe [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-04 10:41 nfsd: terminating on error 104 problem Johan van den Dorpe
2004-03-04 11:11 ` Olaf Kirch
2004-03-04 12:59 ` Johan van den Dorpe
2004-03-05 18:01 ` Johan van den Dorpe
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=403CD391.1010809@framestore-cfc.com \
--to=johan.vandendorpe@framestore-cfc.com \
--cc=linux-kernel@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.