<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Qtree-level exports in CDOT in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Qtree-level-exports-in-CDOT/m-p/58160#M13667</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Allow me to ask a further question that may be easier for someone to answer now that I think I might get it myself.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It looks as though qtree-level exports merely allow you to make access unique to the underlying qtrees within a volume, but access still needs to be allowed at the volume level for all rules defined at the qtree-level.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So access to underlying qtrees can be more restrictive than access at the volume level.&amp;nbsp; But in the case where you want to give more access at the qtree-level than you do the volume-level...it's not possible due to the way junction paths function requiring the hierarchical access.&amp;nbsp; Is this correct?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 01 Jul 2014 12:48:04 GMT</pubDate>
    <dc:creator>bsnyder27</dc:creator>
    <dc:date>2014-07-01T12:48:04Z</dc:date>
    <item>
      <title>Qtree-level exports in CDOT</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Qtree-level-exports-in-CDOT/m-p/58155#M13665</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Anyone able to explain to me how to make them work?&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've tied an export-policy to a qtree w/ a rule allowing a host NFS protocol access - any any any.&amp;nbsp; Getting access denied from the client host when attempting to mount.&amp;nbsp; Tried w/ hostname, FQDN hostname and IP address.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All result in 'access denied by server while mounting'.&amp;nbsp; Adding access at the volume level works though.&amp;nbsp; Maybe I'm missing a step.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unix Permissions: -s-rwxrwxr-x&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 05:34:27 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Qtree-level-exports-in-CDOT/m-p/58155#M13665</guid>
      <dc:creator>bsnyder27</dc:creator>
      <dc:date>2025-06-05T05:34:27Z</dc:date>
    </item>
    <item>
      <title>Re: Qtree-level exports in CDOT</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Qtree-level-exports-in-CDOT/m-p/58160#M13667</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Allow me to ask a further question that may be easier for someone to answer now that I think I might get it myself.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It looks as though qtree-level exports merely allow you to make access unique to the underlying qtrees within a volume, but access still needs to be allowed at the volume level for all rules defined at the qtree-level.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So access to underlying qtrees can be more restrictive than access at the volume level.&amp;nbsp; But in the case where you want to give more access at the qtree-level than you do the volume-level...it's not possible due to the way junction paths function requiring the hierarchical access.&amp;nbsp; Is this correct?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Jul 2014 12:48:04 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Qtree-level-exports-in-CDOT/m-p/58160#M13667</guid>
      <dc:creator>bsnyder27</dc:creator>
      <dc:date>2014-07-01T12:48:04Z</dc:date>
    </item>
    <item>
      <title>Re: Qtree-level exports in CDOT</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Qtree-level-exports-in-CDOT/m-p/58169#M13668</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, this is correct. This is also documented this way. You cannot export nested mounts with less restrictive permissions than parent mounts.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Jul 2014 13:28:14 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Qtree-level-exports-in-CDOT/m-p/58169#M13668</guid>
      <dc:creator>aborzenkov</dc:creator>
      <dc:date>2014-07-01T13:28:14Z</dc:date>
    </item>
  </channel>
</rss>

