All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Mi Jinlong <mijinlong@cn.fujitsu.com>
Cc: "Trond.Myklebust" <trond.myklebust@fys.uio.no>,
	Chuck Lever <chuck.lever@oracle.com>,
	NFSv3 list <linux-nfs@vger.kernel.org>
Subject: Re: [RFC] Should lockd get into grace_period when statd start but not stop?
Date: Fri, 12 Mar 2010 18:08:04 -0500	[thread overview]
Message-ID: <20100312230804.GN13941@fieldses.org> (raw)
In-Reply-To: <4B9A0C7A.1000001@cn.fujitsu.com>

On Fri, Mar 12, 2010 at 05:42:18PM +0800, Mi Jinlong wrote:
> 
> 
> J. Bruce Fields:
> > Our current NFS implementation just isn't designed to be able to shut
> > down some components while leaving others running.
> 
>   Really? But the lockd started with nfs service start, but not nfslock service.
>   And, lockd can't stop with statd at the same time. 
>   Sometimes, the lockd will not synchronous with statd. Maybe this problem is a good example.

I'm sorry, I still don't understand.

Please take a look at section 3.1, 3.2, and 3.3 of the nfs-utils README
file.  That describes the order in which servers should be started and
stopped.

--b.

  reply	other threads:[~2010-03-12 23:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10 10:22 [RFC] Should lockd get into grace_period when statd start but not stop? Mi Jinlong
2010-03-10 18:24 ` J. Bruce Fields
2010-03-11  1:02   ` Mi Jinlong
2010-03-11 15:58     ` J. Bruce Fields
2010-03-12  9:42       ` Mi Jinlong
2010-03-12 23:08         ` J. Bruce Fields [this message]
2010-03-16 10:05           ` Mi Jinlong
2010-03-16 16:56             ` J. Bruce Fields

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=20100312230804.GN13941@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=mijinlong@cn.fujitsu.com \
    --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 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.