From: "Jeff V. Merkey" <jmerkey@drdos.com>
To: Andy <genanr@emsphone.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: TCP NFS to Novell does not work
Date: Fri, 11 Jun 2004 18:03:20 -0600 [thread overview]
Message-ID: <40CA4848.7070509@drdos.com> (raw)
In-Reply-To: <20040611185156.GA26757@thumper2>
Are you using a remote NetWare server running the NFS Server NLM with
NFSv3 from Linux? Try compiling the kernel with NFSv3 disabled and use
NFSv2 instead.
Jeff
Andy wrote:
>Using kernel 2.4.26, I am unable to copy large files to novell over TCP
>NFS. It copies part of the file, the I get a "stale NFS file handle" error.
>I can then delete the file on novell over NFS without a problem. I do not
>have this problem coping to a tru64 mount.
>
>UDP works, but I get corruption in the file. Which I shouldn't get.
>
>Andy
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
prev parent reply other threads:[~2004-06-11 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 18:51 TCP NFS to Novell does not work Andy
2004-06-12 0:03 ` Jeff V. Merkey [this message]
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=40CA4848.7070509@drdos.com \
--to=jmerkey@drdos.com \
--cc=genanr@emsphone.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox