Return-Path: Received: from fieldses.org ([173.255.197.46]:33100 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965013AbcBQU7a (ORCPT ); Wed, 17 Feb 2016 15:59:30 -0500 Date: Wed, 17 Feb 2016 15:59:29 -0500 To: Chuck Lever Cc: "Adamson, Andy" , Martin Houry , "linux-nfs@vger.kernel.org" , Trond Myklebust Subject: Re: "Re: [PATCH RFC Version 1 0/6] Request for Comment: NFS4.1 Session Trunking" Message-ID: <20160217205929.GF10401@fieldses.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 In-Reply-To: From: bfields@fieldses.org (J. Bruce Fields) Sender: linux-nfs-owner@vger.kernel.org List-ID: On Wed, Feb 17, 2016 at 02:06:35PM -0500, Chuck Lever wrote: > > > On Feb 17, 2016, at 9:50 AM, Adamson, Andy > > wrote: Thanks for testing. As Trond > > pointed out, the correct way to indicate multiple hostnames is on > > the mount command line > > > > mount -o minorversion=1 host1,host2,…,hostn:/ / > > It might be more natural for NFSv4.x to use a referral or a pNFS > layout instead. Do you think that's a viable approach? Seems like an easy application for fs_locations{_info?}. It'd need server support too, and I think you probably want this manual method as well for now. I wonder if the server can easily generate a list of IP addresses to advertise automatically? In which case the whole thing would be zero-configuration, which would be nice. pNFS sounds like overkill. --b.