From owner-freebsd-fs@freebsd.org  Fri Oct  7 21:30:42 2016
Return-Path: <owner-freebsd-fs@freebsd.org>
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 B122BC04607
 for <freebsd-fs@mailman.ysv.freebsd.org>; Fri,  7 Oct 2016 21:30:42 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 9FEB1E4B
 for <freebsd-fs@FreeBSD.org>; Fri,  7 Oct 2016 21:30:42 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u97LUgVo029280
 for <freebsd-fs@FreeBSD.org>; Fri, 7 Oct 2016 21:30:42 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 213261] NFSV4 mount misplaces directory name, adding a comma
 ',' character trail to the name, resulting to an error.
Date: Fri, 07 Oct 2016 21:30:42 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 9.3-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: rmacklem@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-213261-3630-oGiCqUhZD4@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-213261-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-213261-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Oct 2016 21:30:42 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213261

Rick Macklem <rmacklem@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rmacklem@FreeBSD.org

--- Comment #1 from Rick Macklem <rmacklem@FreeBSD.org> ---
The directory path for an NFSv4 mount is different than for NFSv2, NFSv3,
depending on what the server's configuration is.

NFSv4 uses a single directory tree built up from all NFS exported file syst=
ems
on the server. For the FreeBSD server, this is routed at the point specified
by the "V4 ..." line in /etc/exports.
For example:
V4: /
- Means that all mount paths are from the root of the server's file system
  tree.
V4: /home
- Means that all mount paths are relative to "/home". In this case:
     server:/ would mount /home on the server.

"man nfsv4" and "man exports" should help clarify this.
(Some say NFSv4 is NFS in name only.)

--=20
You are receiving this mail because:
You are the assignee for the bug.=