All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Troin <phil@fifi.org>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Chip Salzenberg <chip@debian.org>, nfs@lists.sourceforge.net
Subject: Re: Lock recovery doesn't work in debian statd/lockd ordering
Date: 13 Sep 2002 12:22:20 -0700	[thread overview]
Message-ID: <87elbxsnir.fsf@ceramic.fifi.org> (raw)
In-Reply-To: <15743.63908.531152.357021@notabene.cse.unsw.edu.au>

Neil Brown <neilb@cse.unsw.edu.au> writes:

> Hi Chip and NFSers.
> 
>  I just noticed that lock recovery doesn't work with a Debian NFS
>  server.
>  i.e.  server shuts down, restarts, and the client *Doesn't* reclaim
>  the locks.
> 
>  The problem is that statd starts before lockd.
> 
>  What happens is that:
>     statd starts
>       it moves everything from /var/lib/nfs/sm to /var/lib/nfs/sm.bak
>       it notifies each host listed in /var/lib/nfs/sm.bak that the
>         server has restarted
>     statd on the client gets the notification and tells it's local
>         lockd to reclaim locks.
>     lockd on client asked portmap on server for port number for lockd,
>         but lockd hasn't started on the server so there isn't one.  So
>         lockd on the client gives up (maybe it should persist, I'm not
>         sure).
>     Finally lockd on the server starts, but it is too late.
> 
> 
>  I fixed this for myself by moving /etc/rc2.d/S19nfs-common to S21 so
>  that it starts after nfsd and lockd which are started in
>  S20nfs-kernel-server.
> 
>  There should be no problem with statd starting after lockd and lockd
>  doesn't try to talk to statd until it gets the first lock request.

I've opened a debian bug (# 160800) about this.

  -> http://bugs.debian.org/160800

Phil.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  parent reply	other threads:[~2002-09-13 19:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-12  2:19 Lock recovery doesn't work in debian statd/lockd ordering Neil Brown
2002-09-12  4:00 ` Adrian Phillips
2002-09-12  4:49   ` Neil Brown
2002-09-13 16:37     ` H. J. Lu
2002-09-13 19:22 ` Philippe Troin [this message]
2002-09-15 21:44 ` Chip Salzenberg
2002-09-16  1:31   ` unsubcribe Will Stowe

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=87elbxsnir.fsf@ceramic.fifi.org \
    --to=phil@fifi.org \
    --cc=chip@debian.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=nfs@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.