From mboxrd@z Thu Jan 1 00:00:00 1970 From: "J. Bruce Fields" Subject: Re: [RFC] Should lockd get into grace_period when statd start but not stop? Date: Fri, 12 Mar 2010 18:08:04 -0500 Message-ID: <20100312230804.GN13941@fieldses.org> References: <4B9772EB.9010909@cn.fujitsu.com> <20100310182401.GA23340@fieldses.org> <4B98413F.1080609@cn.fujitsu.com> <20100311155857.GC22587@fieldses.org> <4B9A0C7A.1000001@cn.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Trond.Myklebust" , Chuck Lever , NFSv3 list To: Mi Jinlong Return-path: Received: from fieldses.org ([174.143.236.118]:33775 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933368Ab0CLXGj (ORCPT ); Fri, 12 Mar 2010 18:06:39 -0500 In-Reply-To: <4B9A0C7A.1000001@cn.fujitsu.com> Sender: linux-nfs-owner@vger.kernel.org List-ID: 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.