From: Luke Driscoll <news.cis@driscollnewsletter.com>
To: linux-kernel@vger.kernel.org
Subject: Re: NFS on 2.6.0-test9
Date: Mon, 03 Nov 2003 17:13:53 +0000 [thread overview]
Message-ID: <3FA68CD1.80608@driscollnewsletter.com> (raw)
In-Reply-To: <NPhU.42k.19@gated-at.bofh.it>
Måns Rullgård wrote:
> Luke Driscoll <newsregister@driscollnewsletter.com> writes:
>
>
>>On a kernel 2.6.0-test9 as an NFS client I am having trouble transferring
>>data to and from NFS servers. It it extraordinarily slow. I receive the
>>following information in dmesg:
>>
>>nfs warning: mount version older than kernel
>
>
> I see that one, too. Apart from that, it appears to work. Try the
> tcp option, and see if it helps.
>
tcp option seems to have helped, except when attempting to mount a
redhat 9 nfs server. Mount says:
"nfs server reported service unavailable: Address already in use"
next parent reply other threads:[~2003-11-03 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <NN6j.pY.25@gated-at.bofh.it>
[not found] ` <NPhU.42k.19@gated-at.bofh.it>
2003-11-03 17:13 ` Luke Driscoll [this message]
2003-11-03 17:42 ` NFS on 2.6.0-test9 Måns Rullgård
2003-11-03 13:42 Luke Driscoll
2003-11-03 15:52 ` Måns Rullgård
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=3FA68CD1.80608@driscollnewsletter.com \
--to=news.cis@driscollnewsletter.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;
as well as URLs for NNTP newsgroup(s).