All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Tinsley <btinsley@emageon.com>
To: Hurf Sheldon <linux@graphics.cornell.edu>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFS on linux (Redhat) questions
Date: Fri, 09 Aug 2002 13:15:35 -0500	[thread overview]
Message-ID: <3D5406C7.1040001@emageon.com> (raw)
In-Reply-To: 5.1.0.14.2.20020809132700.01b34798@pop.graphics.cornell.edu

1. Upgrade the kernel to 2.4.18-5
2. Upgrade to the latest Intel e1000 drivers (4.3.x) and tune the 
adapter settings in /etc/modules.conf
3. If possible, look into trunking your network connections with Intel 
iANS (some people have a problem with this, it works very well for us)
4. Try using larger rsize and wsize values on the client (8192 is good, 
I've even had success with 32768 - depends on the nature of your beast)
5. Tune network settings in /etc/sysctl.conf (rmem_xxx, wmem_xxx, etc...)
6. Evaluate your choice of underlying filesystem

We use Red Hat 7.3 with NFS on productions systems with PRO/1000 NICs 
(T, F, XT, MT, and MF) and I've never encountered the problems recently 
posted to the mailing list (although there do seem to be some known 
"rare" bugs).


Hurf Sheldon wrote:

> Hi Folks,
> We have a few 4cpu Xeon 550 servers we wanted to make
> central file servers, each with .5tb of ide->scsi raid on them.
> We currently run FreeBSD on our servers; for several reasons,
> Rh7.3 looked like a good replacement.
> Using the standard iso's for Rh 7.3
> Rh 7.3 installed nicely, picking up the Intel 1000 gb interface,
> the 4 cpu's  the ncr and  adaptec scsi interfaces, etc.
>
> Mounting our existing servers on the Rh7.3  (2.4.18-3smp kernel)
> from various FreeBSD systems resulted in timeouts and
> poor performance. Making the Rh7.3 system the server, mounts to
> other Rh7.3 systems and to the FreeBSD systems were not workable.
> Setting rsize, wsize to 1024 made the connections workable but
> trying to set up Rh7.3 nfs install server, where the parameters on the
> boot client can't be set didn't work.
> So, in quick summary:
> Default NFS from FreeBSD systems to the Rh7.3 requires rsize,wsize=1024,
> NFS betwixt Rh7.3 systems also required this to work.
>
> We found your resource pages, subscribed to the newsgroup
> and read the archives. What we found was disconcerting - it appears that
> NFS under Linux is problematic at best.
>
> We would like to use Rh7.3 for our server platforms but we need some 
> guidance
> re: setting up a reliable production machine that we didn't find in 
> the resources - how
> best to get & keep current the pertinent code, build & replace 
> kernels, etc.
>
> What do IBM, HP & Dell do for their Linux server line? Do we want to 
> get Rh
> Enterprise or some other Linux flavor? (reminds me of the "All Unix 
> systems are
> alike, only different" from a decade ago) Or should we stick with the 
> FreeBSD
> for NFS reliability?
>
> We are digesting so if you care to respond directly, please do.
>
> kind regards,
>
> hurf
> Hurf Sheldon
> Program of Computer Graphics     
> 580 Rhodes Hall, Hoy Rd.
> Cornell University 
> Ithaca, N.Y. 14853 
>
> voice:607 255 6713 fax:607 255 0806
> email: hurf@graphics.cornell.edu
> http://www.graphics.cornell.edu/~hurf/ 
> <http://www.graphics.cornell.edu/%7Ehurf/>
>
>
>

-- 
Brian Tinsley
Chief Systems Engineer
Emageon





-------------------------------------------------------
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

      reply	other threads:[~2002-08-09 18:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E17dAjG-0002Sd-00@usw-sf-list2.sourceforge.net>
2002-08-09 17:55 ` NFS on linux (Redhat) questions Hurf Sheldon
2002-08-09 18:15   ` Brian Tinsley [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=3D5406C7.1040001@emageon.com \
    --to=btinsley@emageon.com \
    --cc=linux@graphics.cornell.edu \
    --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.