From 211024e9b657e284f346850e3c8b7b015704dca6 Mon Sep 17 00:00:00 2001 From: Rick Macklem Date: Tue, 25 Dec 2012 22:34:43 +0000 Subject: [PATCH] Attempt to clarify that for ZFS, all file systems under the NFSv4 root must be exported. This is because ZFS checks exports itself. This is a content change. MFC after: 2 weeks --- usr.sbin/mountd/exports.5 | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/usr.sbin/mountd/exports.5 b/usr.sbin/mountd/exports.5 index 75a5121d6673..12935248f1f5 100644 --- a/usr.sbin/mountd/exports.5 +++ b/usr.sbin/mountd/exports.5 @@ -28,7 +28,7 @@ .\" @(#)exports.5 8.3 (Berkeley) 3/29/95 .\" $FreeBSD$ .\" -.Dd July 12, 2011 +.Dd December 23, 2012 .Dt EXPORTS 5 .Os .Sh NAME @@ -311,12 +311,15 @@ For the third form which specifies the NFSv4 tree root, the directory path specifies the location within the server's file system tree which is the root of the NFSv4 tree. All entries of this form must specify the same directory path. -This location can be any directory and does not +For file systems other than ZFS, +this location can be any directory and does not need to be within an exported file system. If it is not in an exported file system, a very limited set of operations are permitted, so that an NFSv4 client can traverse the tree to an exported file system. Although parts of the NFSv4 tree can be non-exported, the entire NFSv4 tree must consist of local file systems capable of being exported via NFS. +All ZFS file systems in the subtree below the NFSv4 tree root must be +exported. NFSv4 does not use the mount protocol and does permit clients to cross server mount point boundaries, although not all clients are capable of crossing the mount points.