From: Johan van den Dorpe <johan.vandendorpe@framestore-cfc.com>
To: Olaf Kirch <okir@suse.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: nfsd: terminating on error 104 problem
Date: Thu, 04 Mar 2004 12:59:46 +0000 [thread overview]
Message-ID: <40472842.8030602@framestore-cfc.com> (raw)
In-Reply-To: <20040304111138.GO22726@suse.de>
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-04 13:07 UTC|newest]
Thread overview: 4+ 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 [this message]
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=40472842.8030602@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox