From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Christian Reis <kiko@async.com.br>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
NFS@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: 2.4.19+trond and diskless locking problems
Date: Fri, 4 Oct 2002 03:13:14 +0200 [thread overview]
Message-ID: <15772.60202.510717.850059@charged.uio.no> (raw)
In-Reply-To: <20021003202602.M3869@blackjesus.async.com.br>
>>>>> " " == Christian Reis <kiko@async.com.br> writes:
>> > kernel:Aug 10 17:39:22 anthem kernel: lockd: cannot
>> > monitor 192.168.99.7
>>
>> Means that the kernel was unable to contact rpc.statd, or that
>> was unable to contact the server's rpc.statd for some reason.
> Hmmm, I wonder if I understand properly. Is the following flow
> correct for the RPC request?
> Client Kernel -> Client rpc.statd -> Server rpc.statd ->
> Server Kernel
That's more or less right, except that the communication is bidirectional.
>> lies with rpc.statd. Can you see any reason in your setup why
>> it should be failing?
> Not really. The clients run rpc.statd 1.0 and the server,
> 1.0.1. Should I start gdbing it to see what is going wrong?
Start by using tcpdump to find out who, in the above chain, is taking
such a long time to respond.
Cheers,
Trond
next prev parent reply other threads:[~2002-10-04 1:08 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 [this message]
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
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=15772.60202.510717.850059@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®