<?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 CIFS access to big volume via junction path on small volume in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/CIFS-access-to-big-volume-via-junction-path-on-small-volume/m-p/24702#M5823</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I noticed the following when playing around with the 8.1 cmode simulator:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create a volume "data" of 100 GB, create a volume "docs" of 500 GB. Put the "docs" volume under the "data" volume via a junction path, then create CIFS shares to both volumes (eg. share them as "data" and "docs").&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When accessing the \\vserver\docs share, one can copy-paste (close to) 500 GB of data into the volume. No problem there.&lt;/P&gt;&lt;P&gt;But when accessing the \\vserver\data share and going into the "docs" directory/junction path, one can only copy-paste (close to) 100 GB of data into this folder, basically the free spare in the parent "data" volume.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This strikes me as odd behavior. So essentially if I want to create a top-level admin-only share to a parent volume containing one or more junction paths to bigger child volumes, my writes to any of those child volumes through the junction paths are limited by the size of the parent volume.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the rationale behind this ? &lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Filip&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 06:04:56 GMT</pubDate>
    <dc:creator>filipsneppe</dc:creator>
    <dc:date>2025-06-05T06:04:56Z</dc:date>
    <item>
      <title>CIFS access to big volume via junction path on small volume</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/CIFS-access-to-big-volume-via-junction-path-on-small-volume/m-p/24702#M5823</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I noticed the following when playing around with the 8.1 cmode simulator:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create a volume "data" of 100 GB, create a volume "docs" of 500 GB. Put the "docs" volume under the "data" volume via a junction path, then create CIFS shares to both volumes (eg. share them as "data" and "docs").&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When accessing the \\vserver\docs share, one can copy-paste (close to) 500 GB of data into the volume. No problem there.&lt;/P&gt;&lt;P&gt;But when accessing the \\vserver\data share and going into the "docs" directory/junction path, one can only copy-paste (close to) 100 GB of data into this folder, basically the free spare in the parent "data" volume.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This strikes me as odd behavior. So essentially if I want to create a top-level admin-only share to a parent volume containing one or more junction paths to bigger child volumes, my writes to any of those child volumes through the junction paths are limited by the size of the parent volume.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the rationale behind this ? &lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Filip&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:04:56 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/CIFS-access-to-big-volume-via-junction-path-on-small-volume/m-p/24702#M5823</guid>
      <dc:creator>filipsneppe</dc:creator>
      <dc:date>2025-06-05T06:04:56Z</dc:date>
    </item>
    <item>
      <title>Re: CIFS access to big volume via junction path on small volume</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/CIFS-access-to-big-volume-via-junction-path-on-small-volume/m-p/24707#M5825</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is bug 578894, which is fixed in 8.2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="active_link" href="http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&amp;amp;Display=578894" title="http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&amp;amp;Display=578894" target="_blank"&gt;http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&amp;amp;Display=578894&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In that public report are several workarounds until the issue is addressed in code.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Apr 2013 13:34:55 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/CIFS-access-to-big-volume-via-junction-path-on-small-volume/m-p/24707#M5825</guid>
      <dc:creator>parisi</dc:creator>
      <dc:date>2013-04-18T13:34:55Z</dc:date>
    </item>
  </channel>
</rss>

