Skip to main content
NetApp Knowledge Base

How to give a client full control to a junctioned volume over NFS, but no access (not even read access) to the root volume of a vserver

Last Updated:

Applies to

Clustered Data ONTAP


In certain NFS scenarios, it is required for clients to be able to access, read, and write (with or without squashing root) a certain junctioned volume, but have no read access to the vserver root volume.

For access to a junctioned volume to be possible, NFSv4 clients always need to have execute permissions on all the junctions in the junction tree, up and including the vserver root volume. Execute permissions on parent objects in the namespace are not required for NFSv3 clients, but mount permissions are required.

The steps that should be followed to allow a client full access to a junctioned volume, but no read access to the root volume are described below:


Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.