From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: "schönfeld / in-medias-res" <schoenfeld@in-medias-res.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ncpfs: Connection invalid / Input-/Output Errors
Date: Wed, 07 Sep 2005 18:24:31 +0200 [thread overview]
Message-ID: <431F143F.2070904@vc.cvut.cz> (raw)
In-Reply-To: <431EF5CD.9050006@in-medias-res.com>
schönfeld / in-medias-res wrote:
> Hi,
>
> thanks for your answere.
> Uhmm... then remains the question: Why should that happen on the first
> machine but not on the second?
Enable displaying of connection watchdog logouts on the server. Do not
use 'intr' mount option. Do not send KILL signal to the connection
which is waiting for reply from server. If you are not sure that your
network infrastructure is fine, use 'hard' mount option to disable
timeouts altogether.
>>To see if this is your problem, insert some printk()s in the relevant
>>ncpfs code (depends whether you are using ipx or tcp/udp as to where)
>
> Well - i'm using IPX. So where do i insert the printk()s? And what kind
> of printk()s should i insert? Please don't think of me as an idiot,
> but i'm just not firm with "kernel hacking".
Into 'ncp_invalidate_conn()', or better, into its callers. One is in
__abort_ncp_connection (invoked for IPX connections when
__ncpdgram_timeout_proc fires), second is in ncp_do_request (if server
reports some problem, or if KILL signal is sent to the process).
Petr
next prev parent reply other threads:[~2005-09-07 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S932080AbVIGI45/20050907085657Z+286@vger.kernel.org>
2005-09-07 11:08 ` ncpfs: Connection invalid / Input-/Output Errors schönfeld / in-medias-res
2005-09-07 12:11 ` Anton Altaparmakov
2005-09-07 14:14 ` schönfeld / in-medias-res
2005-09-07 16:24 ` Petr Vandrovec [this message]
2005-09-09 7:36 ` schönfeld / in-medias-res
2005-09-09 10:46 ` Petr Vandrovec
2005-09-09 11:16 ` schönfeld / in-medias-res
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=431F143F.2070904@vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=schoenfeld@in-medias-res.com \
/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