From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 11 Feb 2009 15:26:34 -0500 To: Jeff Garzik Subject: Re: NFS clients' use of fs_locations? Message-ID: <20090211202634.GA27686@fieldses.org> References: <49932E72.8060209@garzik.org> In-Reply-To: <49932E72.8060209@garzik.org> From: "J. Bruce Fields" Cc: linux-nfs@vger.kernel.org, nfsv4@linux-nfs.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: nfsv4-bounces@linux-nfs.org Errors-To: nfsv4-bounces@linux-nfs.org MIME-Version: 1.0 List-ID: On Wed, Feb 11, 2009 at 03:00:50PM -0500, Jeff Garzik wrote: > According to the NFSv4 spec (section 6.1), regarding fs_locations, > > On first access of the filesystem, the client should obtain the > value of the fs_locations attribute. If, in the future, the > client finds the server unresponsive, the client may attempt to > use another server specified by fs_locations. > > Does any known client actually fail over to another fs_location, as > described here? > > I am implementing the server side of this... AFAICT Linux barely uses > fs_locations, and Solaris just crashes. Yeah, Linux only uses fs_locations when it crosses a mountpoint to a new filesystem and finds that filesystem is only available elsewhere. Maybe AIX? --b. _______________________________________________ NFSv4 mailing list NFSv4@linux-nfs.org http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4