From owner-freebsd-fs@freebsd.org Sat Apr 23 11:51:47 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 40514B193A8 for ; Sat, 23 Apr 2016 11:51:47 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 20E5F1A11 for ; Sat, 23 Apr 2016 11:51:47 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: by mailman.ysv.freebsd.org (Postfix) id 20342B193A7; Sat, 23 Apr 2016 11:51:47 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1FD94B193A6 for ; Sat, 23 Apr 2016 11:51:47 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id C2B871A10; Sat, 23 Apr 2016 11:51:46 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) IronPort-PHdr: 9a23:65X6Mh8w7reLsv9uRHKM819IXTAuvvDOBiVQ1KB91O0cTK2v8tzYMVDF4r011RmSDdWdtKgP17aempujcFJDyK7JiGoFfp1IWk1NouQttCtkPvS4D1bmJuXhdS0wEZcKflZk+3amLRodQ56mNBXsq3G/pQQfBg/4fVIsYL+lSsiN1Y/ri6ibwN76XUZhvHKFe7R8LRG7/036l/I9ps9cEJs30QbDuXBSeu5blitCLFOXmAvgtI/rpMYwuwwZgf8q9tZBXKPmZOx4COUAVHV1e1wysefxtBDFBS6S638YX39exhBNHgXB6Bzgdo/4tCLhv/E70y6fa57YV7cxDA6j5KQjbRbjiyMKMnZt6mTegc90gadzvRWuuhF7246Sa4jDZ6k2Rb/UYd5PHTkJZc1WTSEUR9rkN4Y= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2DQAQB0YBtX/61jaINehAt9Brl/AQ2BdRcLhSJKAoFaFAEBAQEBAQEBZCeCLYIUAQEBAwEBAQEgBCcgCwULAgEIDgoCAg0ZAgInAQkmAQEECAcEARwEiAEIDq5UkQMBAQEBAQEBAwEBAQEBARYEfIUlgX2CToQgAQEFgxiCVgWYD4V7hS6Re48tAh4BAUKEByAwB4c/Nn8BAQE X-IronPort-AV: E=Sophos;i="5.24,522,1454994000"; d="scan'208";a="279746841" Received: from nipigon.cs.uoguelph.ca (HELO zcs1.mail.uoguelph.ca) ([131.104.99.173]) by esa-annu.net.uoguelph.ca with ESMTP; 23 Apr 2016 07:50:36 -0400 Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 9647815F579; Sat, 23 Apr 2016 07:50:36 -0400 (EDT) Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id sMbupUmmi90j; Sat, 23 Apr 2016 07:50:36 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 0FD9815F57B; Sat, 23 Apr 2016 07:50:36 -0400 (EDT) X-Virus-Scanned: amavisd-new at zcs1.mail.uoguelph.ca Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 6_p2zbdaVlEH; Sat, 23 Apr 2016 07:50:35 -0400 (EDT) Received: from zcs1.mail.uoguelph.ca (zcs1.mail.uoguelph.ca [172.17.95.18]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id E8CA315F579; Sat, 23 Apr 2016 07:50:35 -0400 (EDT) Date: Sat, 23 Apr 2016 07:50:35 -0400 (EDT) From: Rick Macklem To: Brian Mueller Cc: fs@freebsd.org, rpokala@freebsd.org Message-ID: <1384504373.75445193.1461412235720.JavaMail.zimbra@uoguelph.ca> In-Reply-To: References: Subject: Re: Add NFSv3 tree root to mountd MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.11] X-Mailer: Zimbra 8.0.9_GA_6191 (ZimbraWebClient - FF18 (Linux)/8.0.9_GA_6191) Thread-Topic: Add NFSv3 tree root to mountd Thread-Index: AdGc+6acZLPrcoy9QQ+IJFb6/cIX0/4KIqRf X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 11:51:47 -0000 Brian Mueller wrote: > Similar to mountd's ability to specify the NFSv4 tree root via the V4: line > in the exports file, I would like to add the ability to specify a NFSv3 tree > root. The goal to have the same exported path for both the V3 and V4. If > you have exports file like the following: > > /foo/bar > V3: /foo/bar > V4: /foo/bar > > NFS clients would mount /foo/bar by running > > mount -t nfs -o ver=3 server:/ /mnt/v3 > mount -t nfs -o ver=4 server:/ /mnt/v4 > > Without the change, the NFS client would need to specify different paths for > v3 and v4 > > mount -t nfs -o ver=3 server:/foo/bar /mnt/v3 > mount -t nfs -o ver=4 server:/ /mnt/v4 > > Feedback appreciated. If there aren't any objections with incorporating this > change into FreeBSD, I will start working on the changes to mountd. > Basically I assume you are planning on using the V3 "/foo/bar" as a prefix that is prepended to the path when a Mount RPC request arrives. I, personally, don't see a problem with this, assuming that things still work the same when the "V3" line isn't in /etc/exports. A couple of comments: - Since NFSv3 doesn't follow server mounts, the results of a V3 mount will still be different than NFSv4 unless there is only one file system under "/foo/bar". --> Maybe adding this will just add to the confusion already present w.r.t. the differences between NFSv3 and NFSv4? (Falsely giving the impression that adding the "V3" line somehow makes them the same?) - In case you haven't looked at it, mountd.c is a beast. You'll have fun adding this change to it. rick > Brian > > Brian Mueller > Panasas Inc. > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >