All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Behnert <abehn@gmx.net>
To: nfs@lists.sourceforge.net
Subject: Re: nfs over TCP stable?
Date: Mon, 05 May 2003 12:49:20 +0200	[thread overview]
Message-ID: <3EB641B0.50903@gmx.net> (raw)
In-Reply-To: <3EB44527.6090005@wanadoo.es>

Xose Vazquez Perez wrote:
> hi,
> 
> Red Hat 9-kernel 2.4.20-9 doesn't include nfs over TCP because they
> said that "it doesn't work good enough in our testing....."
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=88583
> 
> Are there any problems at standard kernels or only at
> mega-patched rh kernels?
> 
> -thanks in advance-
> 
> regards,

(Sorry 'bout my poor English)

Linux NFS server, UNIX clients:
I used 2.2.20 for NFSv3 over UDP for a long time and did some tests
with 2.4.21-rc7 for NFSv3 over TCP. Unfortunately there were a lot of
problems. "Normal" stress tests (mounting, creating some very large
and many small files, copying, ...) showed no problems but CATIA is
running on the clients and CATIA, at least 4.2.2/4.2.4, seems to use
some special fs access methods (sorry, can't be more specific becuse
I simply don't know :) and heavily relies on statd/lockd. With CATIA
running IRIX worked almost without a problem, AIX5L didn't work at all,
HP-UX11 was (and still is) _extremely_ slow, saving/loading a 90 MB
model file takes forever. AIX client behaviour could be fixed with a
"proto=udp" mount option, HP-UX11 couldn't be fixed until now because
it seems to ignore the "proto=udp" mount option I put into /etc/fstab
and the manpages seem to differ from the real behaviour. So apart from
the NFSv3 over TCP problems there seems to be a bug in HP-UX11, at
least in the release that's running here. Log files didn't say anything
relevant, not on the server and also not on the clients. To be honest -
at the moment I don't know what to do to get NFS over TCP to work
reliably and performant with all these client systems.
Next step will be a recompiled kernel 2.4.21-rc7 on the server with
deactivated TCP support for knfsd and I hope that then everything will
work as expected again because it did before with kernel 2.2.20 and UDP
only.

Server is Debian 3.0r1+security, replaced distribution nfs-utils package
with a Debian package built from current 1.0.3 nfs-utils, network 
100MBit, switched.

Regards,
Andreas



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  parent reply	other threads:[~2003-05-05 10:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-03 22:39 nfs over TCP stable? Xose Vazquez Perez
2003-05-03 23:29 ` Greg Lindahl
2003-05-05 10:49 ` Andreas Behnert [this message]
2003-05-05 11:29 ` Steve Dickson
2003-05-07  5:10   ` Neil Brown
2003-05-06  6:57 ` Martin Spott
  -- strict thread matches above, loose matches on Subject: below --
2003-05-05 19:43 Xose Vazquez Perez
2003-05-05 19:49 Xose Vazquez Perez

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=3EB641B0.50903@gmx.net \
    --to=abehn@gmx.net \
    --cc=nfs@lists.sourceforge.net \
    /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.