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: /var/lib/nfs/sm/ files
Date: Wed, 8 Jan 2003 13:46:10 +0100	[thread overview]
Message-ID: <200301081346.10335.trond.myklebust@fys.uio.no> (raw)
In-Reply-To: <20030108095050.C22321@blackjesus.async.com.br>

On Wednesday 08 January 2003 12:50, Christian Reis wrote:
>     - Why don't all the diskless workstations get an entry in that
>       directory while they are running? Right now I have 5 running, and
>       only one has an entry there.

...because only clients that are currently holding POSIX locks will have an 
entry.

>     - Why do most entries' mtime get updated periodically, but a few of
>       the entries go stale with time?

The file should get deleted every time the client releases all locks and 
successfully manages to notify the server that it is stopping monitoring.

>     - Why do some of the stale entries get left over even after the
>       workstations have halted (these ones present the nfs hang issue)?


As I've told you before: 'stale' entries, as you call them, indicate that the 
rpc.statd never managed to notify the server that it should stop monitoring. 
It indicates either the server or the client crashed before the POSIX locks 
held by the client got released, or possibly that the rpc.statd processes 
crashed (or got 'kill -9' ed).

Cheers,
  Trond

  reply	other threads:[~2003-01-08 12:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-07 15:27 Christian Reis
2003-01-07 16:54 ` Trond Myklebust
2003-01-08 11:50   ` Christian Reis
2003-01-08 12:46     ` Trond Myklebust [this message]
2003-01-08 17:14       ` Christian Reis

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=200301081346.10335.trond.myklebust@fys.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®