mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Christian Reis <kiko@async.com.br>
Cc: NFS@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: 2.4.19+trond and diskless locking problems
Date: Wed, 27 Nov 2002 21:31:42 +0100	[thread overview]
Message-ID: <15845.11182.384531.599421@charged.uio.no> (raw)
In-Reply-To: <20021127150828.A12120@blackjesus.async.com.br>

>>>>> " " == Christian Reis <kiko@async.com.br> writes:

     > What can I do to help further debug the issue? Try another
     > kernel version on clients? Server? This is giving me a
     > headache.. :-/

Try to give us a dump of the server lock manager activity when this
problem occurs. Try to do

echo "217" >/proc/sys/sunrpc/nlm_debug

on the server just before the client issues a lock.

Cheers,
  Trond

  reply	other threads:[~2002-11-27 20:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-03 21:44 Christian Reis
2002-10-03 22:47 ` Trond Myklebust
2002-10-03 23:26   ` Christian Reis
2002-10-04  1:13     ` Trond Myklebust
2002-11-20 14:02       ` Christian Reis
2002-11-20 17:02         ` Trond Myklebust
2002-11-27  0:41           ` Christian Reis
2002-11-27  1:14             ` Trond Myklebust
2002-11-27  1:44               ` Christian Reis
2002-11-27 17:08               ` Christian Reis
2002-11-27 20:31                 ` Trond Myklebust [this message]
2002-11-29  1:34                   ` Christian Reis
2002-12-02 14:51                     ` Christian Reis
     [not found]                   ` <20021128232911.G18175@blackjesus.async.com.br>
     [not found]                     ` <200212021921.24330.trond.myklebust@fys.uio.no>
2002-12-04 14:20                       ` Christian Reis
2002-10-04  7:07 ` [NFS] " Juergen Hasch
2002-10-04 13:17   ` Christian Reis
2002-10-04 16:00     ` Juergen Hasch

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=15845.11182.384531.599421@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=NFS@lists.sourceforge.net \
    --cc=kiko@async.com.br \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®