From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Christoph Pittracher <pitt@gmx.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ncpfs input/output error
Date: Thu, 17 Jan 2002 18:16:47 +0100 [thread overview]
Message-ID: <F2BDF7440AF@vcnet.vc.cvut.cz> (raw)
On 17 Jan 02 at 17:48, Christoph Pittracher wrote:
>
> read(3, "\337\375\337\341\273\257\344\n\264\0302%\231\337\233\261"...,
> 512)
> = 512
> write(4, "\337\375\337\341\273\257\344\n\264\0302%\231\337\233\261"...,
> 512)
> = -1 EIO (Input/output error)
> [...]
>
> I don't know why this write fails...
> Any hints?
You should see some complaints in kernel log, or, maybe, on server's
console. In kernel log you should see some 'NCP server not responding' or
'ncp_rpc_call: recv error = NN'. Or maybe you are getting 'An NCP request
with an invalid security signature was received from user <you> at
<your address>. Possible intruder or network corruption.'
You also must not send SIGKILL to processes which are in the middle of
NCP transaction. Because of ncpfs does not use its own thread (or bh)
to implement NCP ping-pong protocol, connection becomes invalid after
such action, as ping-pong was not successfully completed.
Are you sure that you do not have directory restriction
on your directory, and that you are not running some ipxripd which
could remove route to server from your routing tables?
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
P.S.: It is possible to create 2GB file full of data on ncpfs with 2.4.17,
or 4GB file with few patches here...
next reply other threads:[~2002-01-17 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 17:16 Petr Vandrovec [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-17 16:48 ncpfs input/output error Christoph Pittracher
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=F2BDF7440AF@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pitt@gmx.at \
/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