From: Erik Walthinsen <omega@pdxcolo.net>
To: Ian Kent <raven@themaw.net>
Cc: nfs@lists.sourceforge.net
Subject: Re: NAS server avalanche overload
Date: Wed, 03 Mar 2004 21:31:53 -0800 [thread overview]
Message-ID: <1078378313.853.3.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.58.0403041234150.7374@wombat.indigo.net.au>
On Wed, 2004-03-03 at 20:39, Ian Kent wrote:
> Bumping the number of threads to 32 or 64 or more would be the first
> thing I would try.
Only problem is that if the spike occurs anyway, the load will be 33 or
65 instead of 17. I don't know if it's ctxswitching itself to death
while all these nfsd's are blocking, but if so, doubling or quadrupling
the number of blocked processes will just make the spike worse.
Also, I've learned to be extremely careful about messing with nfsd while
clients are connected. I've had cases where just running exportfs
*seems* to have permanently killed the client's session, yet the client
of course still has the filesystem mounted. This required a complete
*hard* kill of every UML instance on the client, which did a significant
amount of damage to the filesystems that were mounted at the time.
- Omega
aka Erik Walthinsen
omega@pdxcolo.net
-------------------------------------------------------
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-04 5:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 8:31 NAS server avalanche overload Erik Walthinsen
2004-03-03 22:02 ` Erik Walthinsen
2004-03-04 0:04 ` Greg Banks
2004-03-04 0:20 ` Erik Walthinsen
2004-03-04 1:40 ` Greg Banks
2004-03-04 2:17 ` Trond Myklebust
2004-03-04 4:39 ` Ian Kent
2004-03-04 5:31 ` Erik Walthinsen [this message]
2004-03-04 5:47 ` Greg Banks
2004-03-04 14:38 ` Ian Kent
[not found] <482A3FA0050D21419C269D13989C61130435DCCB@lavender-fe.eng.netapp.com>
2004-03-03 22:34 ` Erik Walthinsen
-- strict thread matches above, loose matches on Subject: below --
2004-03-04 2:07 Lever, Charles
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=1078378313.853.3.camel@localhost \
--to=omega@pdxcolo.net \
--cc=nfs@lists.sourceforge.net \
--cc=raven@themaw.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.