From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 17/18] xfs: implement pnfs export operations Date: Fri, 9 Jan 2015 12:41:59 +0100 Message-ID: <20150109114159.GA25728@lst.de> References: <1420561721-9150-1-git-send-email-hch@lst.de> <1420561721-9150-18-git-send-email-hch@lst.de> <20150107002434.GG31508@dastard> <20150107104010.GD28783@lst.de> <20150107211140.GC25000@dastard> <20150108124327.GA15222@lst.de> <20150108210405.GG25000@dastard> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: "J. Bruce Fields" , linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org, Jeff Layton , xfs@oss.sgi.com To: Dave Chinner Return-path: Content-Disposition: inline In-Reply-To: <20150108210405.GG25000@dastard> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com List-Id: linux-fsdevel.vger.kernel.org On Fri, Jan 09, 2015 at 08:04:05AM +1100, Dave Chinner wrote: > > If the client sends the opaqueue device ID that contains the generation > > after the grow to a server that had crashed / restarted the server > > will reject it as the server starts at zero. The causes the client > > to get a new, valid device ID from the server. > > But if the server fs has a generation number of zero when it > crashes, how does the client tell that it needs a new device ID from > the server? > > > Unlike the NFS file hadles which are persistent the device IDs are volatile > > handles that can go away (and have really horrible life time rules..). > > Right. How the clients detect that "going away" when the device > generation is zero both before and after a server crash is the > question I'm asking.... The server tells the client by rejecting the operation using the device ID. _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs