From: Johan van den Dorpe <johan.vandendorpe@framestore-cfc.com>
To: Johan van den Dorpe <johan.vandendorpe@framestore-cfc.com>
Cc: Olaf Kirch <okir@suse.de>, nfs@lists.sourceforge.net
Subject: Re: nfsd: terminating on error 104 problem
Date: Fri, 05 Mar 2004 18:01:58 +0000 [thread overview]
Message-ID: <4048C096.3090803@framestore-cfc.com> (raw)
In-Reply-To: <40472842.8030602@framestore-cfc.com>
I tried out the patch today, rebooted with the new kernel at 9:42am
Then, we started getting these messages (which we were having before but
didn't cause any noticable problems)
Mar 5 10:05:00 ps30 kernel: nfsd: peername failed (err 107)!
After a few hours, we started getting the terminating on error 104 errors:
Mar 5 13:56:49 ps30 kernel: nfsd: terminating on error 104
Until finally the server crashed, refusing input from the console. There
were no messages on the console apart from the above nfsd errors. This
is the last syslog entry
Mar 5 17:10:10 ps30 rpc.mountd: Caught signal 15, un-registering and
exiting.
Mar 5 17:10:10 ps30 nfs: rpc.mountd shutdown succeeded
While the server was up we recieved 112 peername failed (err 107)
messages, and 5 terminating on error 104 messages.
If you want any more info please tell me what it is you need.
Otherwise have a good weekend!
Thanks,
Johan.
Johan van den Dorpe wrote:
> Olaf Kirch wrote:
>
>> On Thu, Mar 04, 2004 at 10:41:02AM +0000, Johan van den Dorpe wrote:
>>
>>> 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.
>>
>>
>>
>> 104 is ECONNRESET, this means the client reset the connection.
>> The server should really clean up the socket in this case.
>>
>> Does the attached patch help?
>> Beware - totally untested, better not try this on a production
>> machine :)
>
>
> Thanks very much for this... I'm going to run a test with this patch and
> get back to you with results after.
>
>
--
Johan van den Dorpe
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-03-05 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-25 16:55 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=4048C096.3090803@framestore-cfc.com \
--to=johan.vandendorpe@framestore-cfc.com \
--cc=nfs@lists.sourceforge.net \
--cc=okir@suse.de \
/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.