From owner-freebsd-fs@freebsd.org Sat Apr 23 14:28:31 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 DF6D4B197CD for ; Sat, 23 Apr 2016 14:28:31 +0000 (UTC) (envelope-from alex.burlyga.ietf@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id BEB1C1330 for ; Sat, 23 Apr 2016 14:28:31 +0000 (UTC) (envelope-from alex.burlyga.ietf@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id BA56AB197CB; Sat, 23 Apr 2016 14:28:31 +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 B9F60B197C9 for ; Sat, 23 Apr 2016 14:28:31 +0000 (UTC) (envelope-from alex.burlyga.ietf@gmail.com) Received: from mail-vk0-x243.google.com (mail-vk0-x243.google.com [IPv6:2607:f8b0:400c:c05::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 73397132F; Sat, 23 Apr 2016 14:28:31 +0000 (UTC) (envelope-from alex.burlyga.ietf@gmail.com) Received: by mail-vk0-x243.google.com with SMTP id o133so7231048vka.1; Sat, 23 Apr 2016 07:28:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=JGcr4qw+M2uHVtc4zgQXCjmxcrFlqDo9qd9YfCAVRuc=; b=FV7zlt266ntTB25k2PzIovUOrRAHAQeQDkK824Aqh/zuSEmaOb0DVUikEVI3zSYMKO ReJdQVjgmhGXet5vUcI/PAZzvmDrTDY1UQ9vLpDhmg42S+yLd3DAVbQwxuupfdJ82pgG XpHo2IQRFXYAOzQ5586D8Njk3gT9g2L7TxzgaRdYZ+UXRHh8utLk7uGzzro07vPeQ37F GcAQm9wNJ5gfql5/Jz0PXA6PvVrPzyPdgFytCIo0X3bzfbGi8SINapwtySizQxKBjMPr P59ZVQk1YvJPS7OTtOmVxH5/wjzk4t4Ldyy1LsJTfTcsruK3m0lV352cGHw7C5mhjsiL 4NxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=JGcr4qw+M2uHVtc4zgQXCjmxcrFlqDo9qd9YfCAVRuc=; b=LofKfQk2XHnlgLUoYlha6B+l8ISW7Y6oMwxFoCtSxsSchISZG/C02kF7AWLwyZVKCe cDjZBdVHN15fB7pu7EqTTzJsN2QS7T6XFe0L2TVZAmqtkyhXXIIr7TdMM2req77z1BPO 51Uq/mGKvlFJJlk8b6sQ+m57+Gbg5PSj0BBzuQKQHXWRUpZFqHppxDSoTMJWIm/tBnEm 7bTsssKYq2rNuDSVQksVJ5sfi+ByW8WeBcvqpsO3yR6+/rM/NLRjlG42cE4BCeGSRQ0K sNPbPUcrOFQtBAiWca7g7x+Uq1pLCKFFInQDR3UwaOiuJnD7Vho8DGu+6r4NlHc4QSr9 Z/uw== X-Gm-Message-State: AOPr4FWYHl7Dq3xlTJ0qdHZmPdxG2aGV02Icly+vXemOZ/L4rRS/2XTWCKEJv+ansrtyJQWaVIBGcQQcTuCfew== MIME-Version: 1.0 X-Received: by 10.31.47.88 with SMTP id v85mr14352897vkv.118.1461421710581; Sat, 23 Apr 2016 07:28:30 -0700 (PDT) Received: by 10.103.19.199 with HTTP; Sat, 23 Apr 2016 07:28:30 -0700 (PDT) Received: by 10.103.19.199 with HTTP; Sat, 23 Apr 2016 07:28:30 -0700 (PDT) In-Reply-To: <1384504373.75445193.1461412235720.JavaMail.zimbra@uoguelph.ca> References: <1384504373.75445193.1461412235720.JavaMail.zimbra@uoguelph.ca> Date: Sat, 23 Apr 2016 07:28:30 -0700 Message-ID: Subject: Re: Add NFSv3 tree root to mountd From: "alex.burlyga.ietf alex.burlyga.ietf" To: Rick Macklem Cc: Brian Mueller , fs@freebsd.org, rpokala@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 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 14:28:32 -0000 On Apr 23, 2016 04:51, "Rick Macklem" wrote: > > 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?) Agreed, also when testing -actual option on netapp filers(maybe that's the way to go?) we run into problems with some automounters. Quick look at the current freebsd, Linux, and Mac OS X does not reveal any problems, perhaps it was some exotic ones like AIX? Also for v3 adding command line option that make all exports relative to that path, ala webnfs, would be simpler way to go? > - In case you haven't looked at it, mountd.c is a beast. You'll have fun adding > this change to it. Doing command line option or adding another export option I think is simpler way. > > 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" > > > _______________________________________________ > 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"