From: Olaf Kirch <okir@suse.de>
To: Chip Salzenberg <chip@pobox.com>
Cc: Neil Brown <neilb@cse.unsw.edu.au>, nfs@lists.sourceforge.net
Subject: Re: Debian Bug#235886: nfs-kernel-server inducing load of 8-9 with no good reason for Linux 2.6 clients
Date: Fri, 19 Mar 2004 09:48:08 +0100 [thread overview]
Message-ID: <20040319084808.GA25649@suse.de> (raw)
In-Reply-To: <20040318210943.GK3605@perlsupport.com>
On Thu, Mar 18, 2004 at 04:09:43PM -0500, Chip Salzenberg wrote:
> Neil (or someone), what should I tell this user?
They should enable NFS and RPC debugging on the client when this problem
occurs, put the bzipped logs somewhere and send a pointer to this list.
To turn on debugging, do this
echo 65535 > /proc/sys/sunrpc/nfs_debug
echo 65535 > /proc/sys/sunrpc/rpc_debug
If something in the RPC client is going berserk this logs will probably
grow like crazy. It may be helpful to kill syslog and
"cat /proc/kmsg > /tmp/nfs.log" directly. Or even use "head -10000"
instead of cat.
Olaf
--
Olaf Kirch | Stop wasting entropy - start using predictable
okir@suse.de | tempfile names today!
---------------+
-------------------------------------------------------
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-19 8:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 21:09 Debian Bug#235886: nfs-kernel-server inducing load of 8-9 with no good reason for Linux 2.6 clients Chip Salzenberg
2004-03-19 0:08 ` Trond Myklebust
2004-03-19 8:48 ` Olaf Kirch [this message]
2004-03-19 8:49 ` Olaf Kirch
2004-03-19 11:53 ` Bernd Schubert
2004-03-19 12:03 ` Olaf Kirch
2004-03-22 0:25 ` Neil Brown
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=20040319084808.GA25649@suse.de \
--to=okir@suse.de \
--cc=chip@pobox.com \
--cc=neilb@cse.unsw.edu.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox