<?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: Limit cifs path length in ontap 8.3.2 in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Limit-cifs-path-length-in-ontap-8-3-2/m-p/128460#M27846</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can use a vscan server to&amp;nbsp;setup path length limit. Refer&amp;nbsp;&lt;A href="http://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&amp;amp;Display=107770" target="_blank"&gt;http://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&amp;amp;Display=107770&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 27 Feb 2017 06:14:13 GMT</pubDate>
    <dc:creator>Sahana</dc:creator>
    <dc:date>2017-02-27T06:14:13Z</dc:date>
    <item>
      <title>Limit cifs path length in ontap 8.3.2</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Limit-cifs-path-length-in-ontap-8-3-2/m-p/128308#M27808</link>
      <description>&lt;P&gt;Hi folks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;is there a way to limit the path length for cifs shares in data ontap (currently running 8.3.2P4)?&lt;/P&gt;&lt;P&gt;We've problems with our Intellisnap Backup on miltiple cifs shares cause of&amp;nbsp; pathes &amp;gt; 260 digits.&lt;/P&gt;&lt;P&gt;As workaround we've configured Intellisnap to skip the catalog phase.&lt;/P&gt;&lt;P&gt;My idea was to limit the path length to &amp;lt; 260 digits for future cifs shares.&lt;/P&gt;&lt;P&gt;Is there any way to realise this?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 15:25:35 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Limit-cifs-path-length-in-ontap-8-3-2/m-p/128308#M27808</guid>
      <dc:creator>Tom29</dc:creator>
      <dc:date>2025-06-04T15:25:35Z</dc:date>
    </item>
    <item>
      <title>Re: Limit cifs path length in ontap 8.3.2</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Limit-cifs-path-length-in-ontap-8-3-2/m-p/128460#M27846</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can use a vscan server to&amp;nbsp;setup path length limit. Refer&amp;nbsp;&lt;A href="http://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&amp;amp;Display=107770" target="_blank"&gt;http://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&amp;amp;Display=107770&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 27 Feb 2017 06:14:13 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Limit-cifs-path-length-in-ontap-8-3-2/m-p/128460#M27846</guid>
      <dc:creator>Sahana</dc:creator>
      <dc:date>2017-02-27T06:14:13Z</dc:date>
    </item>
    <item>
      <title>Re: Limit cifs path length in ontap 8.3.2</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Limit-cifs-path-length-in-ontap-8-3-2/m-p/129596#M28190</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thats a great idea, cause of Company requirements virus scanning&lt;/P&gt;&lt;P&gt;of our cifs shares is already enabled, but the requirement is to disable&lt;/P&gt;&lt;P&gt;mandatory scan. We had some issues with enabled mandatory scan in the past.&lt;/P&gt;&lt;P&gt;Is there a other way to limit path length?&lt;/P&gt;</description>
      <pubDate>Thu, 30 Mar 2017 09:47:44 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Limit-cifs-path-length-in-ontap-8-3-2/m-p/129596#M28190</guid>
      <dc:creator>Tom29</dc:creator>
      <dc:date>2017-03-30T09:47:44Z</dc:date>
    </item>
    <item>
      <title>Re: Limit cifs path length in ontap 8.3.2</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Limit-cifs-path-length-in-ontap-8-3-2/m-p/129599#M28192</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;By design the windows client will not allow the users to create / move files or folders that commulate to such long path.&lt;/P&gt;&lt;P&gt;when does it&amp;nbsp;allow it? when it' can't&amp;nbsp;determine it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So you need to aim for having the Intellisnap to use the same path or shorter one then what the client uses.&amp;nbsp;either by&amp;nbsp;different share name. not using FQDN. setup a cname. get somehow Intellisnap to mount it, &amp;nbsp; or maybe&amp;nbsp;change how the clients accessing it to be long&amp;nbsp;enough for windows to block it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;if you try to limit the path in the filer itself, that again relative to how the filer see the path, and not 1:1 match to how the user and not how Intellisnap exactly see it (unless you hard code it in your&amp;nbsp;solution whatever it will be) .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Gidi&lt;/P&gt;</description>
      <pubDate>Thu, 30 Mar 2017 11:48:19 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Limit-cifs-path-length-in-ontap-8-3-2/m-p/129599#M28192</guid>
      <dc:creator>GidonMarcus</dc:creator>
      <dc:date>2017-03-30T11:48:19Z</dc:date>
    </item>
  </channel>
</rss>

