Linux NFS development
 help / color / mirror / Atom feed
From: Haakon Riiser <haakon.riiser@fys.uio.no>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: "Server not responding" after periods of client inactivity
Date: Tue, 9 Aug 2005 21:06:34 +0200	[thread overview]
Message-ID: <20050809190634.GA5779@fox.upc.no> (raw)
In-Reply-To: <1122735345.8248.28.camel@lade.trondhjem.org>

Trond,

>> Source  Time  Packets
>> ------  ----  -------
>> client  0.00  V3 ACCESS Call, FH:0x02120000
>> client  0.10  [Retransmission of #1] V3 ACCESS Call, FH:0x02120000
>> client  0.31  [Retransmission of #1] V3 ACCESS Call, FH:0x02120000
>> client  0.71  [Retransmission of #1] V3 ACCESS Call, FH:0x02120000
>> client  1.53  [Retransmission of #1] V3 ACCESS Call, FH:0x02120000
>> client  3.16  [Retransmission of #1] V3 ACCESS Call, FH:0x02120000
>> client  6.42  [Retransmission of #1] V3 ACCESS Call, FH:0x02120000
>> client  7.12  [Retransmission of #1] V3 ACCESS Call, FH:0x02120000
>> client  8.52  [Retransmission of #1] V3 ACCESS Call, FH:0x02120000
>> client 11.32  [Retransmission of #1] V3 ACCESS Call, FH:0x02120000
>> server 15.30  V3 ACCESS Reply
> 
> This is a different problem that has nothing to do with connecting. If
> the client can send RPC requests, then the connection has clearly been
> set up.
> 
> If I were you, I'd look into what "mountd" is up to on the server when
> this happens. The server will just silently drop packets if mountd is
> slow to authorise the client.

OK, I've been trying for some time to reproduce the bug while
stracing mountd on the server, but it seems impossible to do it.
If I do

  strace -p $(pidof rpc.mountd)

the bug never occurs.  If I try to start strace immediately after
the hang begins, strace doesn't attach until the hang is over.
That is, it takes approximately 15 seconds (the entire duration of
the hang) before the

  Process <PID> attached - interrupt to quit

message is displayed and anything else is printed by strace.  Does
this tell you anything?

-- 
 Haakon


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2005-08-09 19:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-14 21:25 "Server not responding" after periods of client inactivity Haakon Riiser
2005-07-30 13:10 ` Haakon Riiser
2005-07-30 14:15   ` Trond Myklebust
2005-07-30 14:32     ` Haakon Riiser
2005-07-30 14:55       ` Trond Myklebust
2005-08-09 19:06         ` Haakon Riiser [this message]
2005-08-09 19:14           ` Trond Myklebust
2005-08-09 19:22             ` Haakon Riiser
2005-08-09 20:32             ` Haakon Riiser
2005-08-09 20:59               ` Trond Myklebust
2005-08-09 22:24                 ` Haakon Riiser
  -- strict thread matches above, loose matches on Subject: below --
2005-07-14 12:34 Haakon Riiser

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=20050809190634.GA5779@fox.upc.no \
    --to=haakon.riiser@fys.uio.no \
    --cc=nfs@lists.sourceforge.net \
    --cc=trond.myklebust@fys.uio.no \
    /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