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:22:24 +0200	[thread overview]
Message-ID: <20050809192224.GA6006@fox.upc.no> (raw)
In-Reply-To: <1123614892.8245.166.camel@lade.trondhjem.org>

Trond,

> Have you tried getting a thread dump when it happens?
> echo "t" > /proc/sysrq-trigger
> on the server then scour through the 'dmesg' output until you find out
> where mountd is hiding.

Haven't tried that yet, but I'll get right on it.  (That is, in an
hour or two, since that's about how long I have to wait before the
bug occurs. :-)

-- 
 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:22 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
2005-08-09 19:14           ` Trond Myklebust
2005-08-09 19:22             ` Haakon Riiser [this message]
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=20050809192224.GA6006@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