From: Jeff Smith <jeff@atheros.com>
To: Eric Whiting <ewhiting@amis.com>
Cc: nfs@lists.sourceforge.net, Ryan Sweet <rsweet@atos-group.nl>
Subject: Re: 2.4.18 knfsd load spikes
Date: Thu, 16 May 2002 11:19:07 -0700 [thread overview]
Message-ID: <3CE3F81B.50FC7F61@atheros.com> (raw)
In-Reply-To: 3CE3F2A4.B326BC5A@amis.com
It is exactly as you describe. Before this started happening, I would run 16
nfsd threads. And when it started happening the load would creep up to 16 as
the server grinds to a halt. To mitigate this, I've dropped down to 2 nfsd
threads so that the machine does not die before I can locate and kill the
"offending" job.
Jeff
Eric Whiting wrote:
>
> I see the load spikes as well. A ps shows the nfsd processes in the 'DW'
> state. DW isn't bad, but when it sits there a long time then the load
> jumps up. (could be disk or network related I think?) This seems similar
> to what you describe here. Does the load average ramp up to the number
> of nfsd threads?
>
> eric
>
> Jeff Smith wrote:
> >
> > We are running ext2 filesystems on a Supermicro dual P3 with Serverworks HE
> > chipset. As best I can tell (which probably does not count for much), the CPU
> > load comes from all the nfsd's holding off requests while waiting for a cache
> > flush. It happens whenever a particular job is run which slowly reads and
> > extends a very large file. When we suspend the job, every thing returns to
> > normal. When we resume the job, everything continues to run normally for a
> > while, but soon begins to bog down the fileserver again.
> >
> > Anyway, I hope you are right that you are experiencing a different problem.
> > Scheduling downtime around here is difficult, but hopefully in the next few
> > weeks I will be able to upgrade the fileservers to 2.4.18 (or 2.4.19?). In the
> > mean time, I'm trying to build a test machine to replicate the problem (and,
> > hopefully, verify the fix).
> >
--
Jeff Smith Atheros Communications, Inc.
Hardware Manager 529 Almanor Avenue
(408) 773-5257 Sunnyvale, CA 94086
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-05-16 18:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 12:11 Stale NFS file handle with 2.4.17 / 2.4.18 Ulrich Hochholdinger
2002-05-14 13:05 ` OOPS: in kernel rpc.mountd with IRIX client patch Ryan Sweet
2002-05-15 12:53 ` 2.4.18 knfsd load spikes Ryan Sweet
2002-05-15 21:44 ` Jeff Smith
2002-05-16 7:52 ` Ryan Sweet
2002-05-16 16:30 ` Jeff Smith
2002-05-16 17:55 ` Eric Whiting
2002-05-16 18:19 ` Jeff Smith [this message]
2002-05-17 9:46 ` 2.4.18 disk i/o load spikes was: " Ryan Sweet
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=3CE3F81B.50FC7F61@atheros.com \
--to=jeff@atheros.com \
--cc=ewhiting@amis.com \
--cc=nfs@lists.sourceforge.net \
--cc=rsweet@atos-group.nl \
/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.