From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: linux-nfs-owner@vger.kernel.org Received: from minas.ics.muni.cz ([147.251.4.40]:37665 "EHLO minas.ics.muni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756223Ab2DJM4Z (ORCPT ); Tue, 10 Apr 2012 08:56:25 -0400 Date: Tue, 10 Apr 2012 14:55:52 +0200 From: Lukas Hejtmanek To: Jeff Layton Cc: linux-nfs@vger.kernel.org, jiri.horky@cesnet.cz Subject: Re: NFSv4 high availability setups Message-ID: <20120410125552.GC5074@ics.muni.cz> References: <20120405103124.GV4752@ics.muni.cz> <20120405073901.63d1c749@tlielax.poochiereds.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 In-Reply-To: <20120405073901.63d1c749@tlielax.poochiereds.net> Sender: linux-nfs-owner@vger.kernel.org List-ID: Hi Jeff, On Thu, Apr 05, 2012 at 07:39:01AM -0400, Jeff Layton wrote: > > As I understand, NFS4 uses state dir somewhere in /var/lib/nfs/rpc_pipefs. > > > > You're probably thinking of /var/lib/nfs/v4recovery. yes, sorry for confusion. > > Can we put this state dir on a shared volume so that this state dir is common > > for all the front-ends serving the same content? Is is supposed to work and > > NFSv4 can merge its state with existing state on a shared disk? > > > > Not properly, no. nfsd expects to have complete control over that > directory. There's no locking or merging of the data there. A node will > also clean that directory out in some cases, and that will throw your > state tracking off. Thank you for information. Is there any (preferably simple) way to demonstrate that this does not work properly? E.g., if I share the same export through two or more NFSv4 front-ends that share the v4recovery directory, do I trigger problems with this tool http://nfsv4.bullopensource.org/tools/tests/locktest.php? -- Lukáš Hejtmánek