From: Charles-Edouard Ruault <ce@idtect.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: csc@cadence.com, nfs@lists.sourceforge.net
Subject: Re: Re: Linux 2.4.25, nfs client hangs when talking to a MacOS nfs server.
Date: Wed, 17 Mar 2004 20:28:52 +0100 [thread overview]
Message-ID: <4058A6F4.6070408@idtect.com> (raw)
In-Reply-To: <1079547364.3047.27.camel@lade.trondhjem.org>
Trond Myklebust wrote:
>P=E5 on , 17/03/2004 klokka 13:01, skreiv Chris Croswhite:
> =20
>
>>I have seen similar issues, but with slowlaris NFS server to linux.=20
>>Never was able to resolve the issue and so moved to linux NFS server. =20
>>
>>I am willing to spend sometime on this issue if Trond can give me some
>>assistance? I can detail the issue if you have you are available.
>> =20
>>
>
>It's very simple: if you using UDP as the transport mechanism, then
>packets can (and *will*) be lost.
> =20
>
yep, that's why i tried switching to TCP ... but with no better result.
>This is particularly true if you are working across a net which mixes
>network speeds, since the switches have to queue data when going from
>the fast to the slower net: once this queue has built up to the point
>where the switch runs out of memory, it will start dropping incoming
>packets.
>
>IOW: this is not an NFS client bug, it is a network design bug.
>
> =20
>
We'll see if this disappears after we've finished migrating the network=20
to 1Gbps
>In these environments you *must* use TCP, since that has congestion
>control capabilities baked into the protocol...
>
>For more detailed info on how to deal with this sort of problem, I
>suggest the NFS FAQ and HOWTO: see http://nfs.sourceforge.net/
>
> =20
>
I'll definitely have a look and try again with TCP just in case i can=20
capture a different error log.
Thanks again for the info.
>Cheers,
> Trond
> =20
>
-------------------------------------------------------
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-17 19:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 10:44 Linux 2.4.25, nfs client hangs when talking to a MacOS nfs server Charles-Edouard Ruault
2004-03-17 16:58 ` Trond Myklebust
2004-03-17 17:41 ` Charles-Edouard Ruault
2004-03-17 17:41 ` Charles-Edouard Ruault
2004-03-17 17:41 ` Charles-Edouard Ruault
2004-03-17 17:59 ` arithmetic functions for linux driver VINOD GOPAL
2004-03-17 18:11 ` John Bradford
2004-03-17 18:15 ` VINOD GOPAL
2004-03-17 18:50 ` Richard B. Johnson
2004-03-17 20:27 ` John Bradford
2004-03-17 18:17 ` Chris Friesen
2004-03-17 18:36 ` Richard B. Johnson
2004-03-17 23:21 ` Peter Williams
2004-03-17 18:01 ` Re: Linux 2.4.25, nfs client hangs when talking to a MacOS nfs server Chris Croswhite
2004-03-17 18:16 ` Trond Myklebust
2004-03-17 19:28 ` Charles-Edouard Ruault [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-17 19:56 Lever, Charles
2004-03-18 16:53 ` Charles-Edouard Ruault
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=4058A6F4.6070408@idtect.com \
--to=ce@idtect.com \
--cc=csc@cadence.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.