From: Luis Cano <Luis.Cano@noaa.gov>
To: nfs@lists.sourceforge.net
Subject: nfsd problem?
Date: Thu, 28 Mar 2002 16:15:01 -0500 [thread overview]
Message-ID: <3CA387D5.6050709@noaa.gov> (raw)
Hello,
Here is my configuration:
- One Raizone, dual processors PIII, 1.5g RAM, running 2.4.16-12smp,
servicing as a NFS server, exporting a reiser filesystem.
- Five Dells 2450, dual processors PIII, 1g RAM, running 2.4.3-12smp,
nfs-utils 0.3.1, mounting the raidzone reiser filesystem via NFS:
rzdm:/home/ftp on /var/ftp/pub type nfs
(ro,noatime,rsize=8192,wsize=8192,hard,intr,nolock,addr=x.x.x.x)
rzdm:/home/www on /var/www type nfs
(rw,sync,noatime,rsize=8192,wsize=8192,hard,intr,nolock,addr=x.x.x.x)
where x.x.x.x is the ip of the raidzone.
The five dell servers are serving as ftp/web servers and front ended
with a load balancer for ftp and http traffic. During peak periods, the
dell server load average climbs to over 400 and ftp throughput
progressively drops from 7.6Mbytes per second to 1.5Mbytes per second.
If we restart NFSD on the raidzone, the dell servers load average drops
to less than 2.5 and ftp throughput increases to the normal 7.6Mbytes
per second. It takes about a day for the load average to climb up again
and ftp throughput to decrease.
Is this a NFSD problem with 2.4.16? Is there something I can look at or
other information needed to determine the problem?
Thank you and appreciate any help.
Luis Cano
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2002-03-28 21:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3CA387D5.6050709@noaa.gov \
--to=luis.cano@noaa.gov \
--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.