All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Ryan <andrewr@collab.net>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: nfs@lists.sourceforge.net
Subject: Re: troubling interaction with quotas and nfs
Date: Tue, 09 Apr 2002 20:16:20 -0700	[thread overview]
Message-ID: <3CB3AE84.3A7531B7@collab.net> (raw)
In-Reply-To: 15538.29176.579826.727109@notabene.cse.unsw.edu.au

Neil Brown wrote:

>
> You could also
>    echo 32 > /proc/sys/sunrpc/nfsd_debug
> and watch for
>     "nfsd: write complete err=%d"
> messages in the kernel log.  These will tell you whether nfsd thinks
> it got an error for the write.

Can you elaborate on what the various values one could write to
/proc/sys/sunrpc/nfsd_debug and what you would get with different values in
terms of logging? This sounds like something that could be useful to many
others and included in the HOWTO or FAQ as well. I've checked the kernel docs
and they basically say to 'use the source,' but since we have some of the
core NFS client/server developers here perhaps someone can offer a few hints
for people debugging NFS configurations.

Also, is there any known or performance or stability hit to running with
NFS debug on?


thanks,
andrew


_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  parent reply	other threads:[~2002-04-10  3:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-09  4:19 troubling interaction with quotas and nfs seth vidal
2002-04-09  4:45 ` Neil Brown
2002-04-09 15:19   ` seth vidal
2002-04-10  3:16   ` Andrew Ryan [this message]
2002-04-12  3:04     ` 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=3CB3AE84.3A7531B7@collab.net \
    --to=andrewr@collab.net \
    --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 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.