From: Erik Walthinsen <omega@pdxcolo.net>
Subject: Re: NAS server avalanche overload
Date: Wed, 03 Mar 2004 21:31:53 -0800
Sender: nfs-admin@lists.sourceforge.net
Message-ID: <1078378313.853.3.camel@localhost>
References: <1078302718.825.67.camel@localhost>
	 <1078351343.821.28.camel@localhost> <20040304000438.GA25910@sgi.com>
	 <1078359638.813.71.camel@localhost> <404688FE.69592A2A@melbourne.sgi.com>
	 <Pine.LNX.4.58.0403041234150.7374@wombat.indigo.net.au>
Mime-Version: 1.0
Content-Type: text/plain
Cc: nfs@lists.sourceforge.net
To: Ian Kent <raven@themaw.net>
In-Reply-To: <Pine.LNX.4.58.0403041234150.7374@wombat.indigo.net.au>
Errors-To: nfs-admin@lists.sourceforge.net

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