<?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: no_i2p volume option in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/no-i2p-volume-option/m-p/47838#M4362</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;A while back I ran a bunch of&amp;nbsp; upgrades from 7.0 -- which 7.1 I believe was the first release with i2p. Initially it consumed a large amount of system resources to complete the initial i2p wafl scan. With some of the nodes, this was not bearable, so it was disabled. I have since enabled many of them, and did not notice any significant improvement after the scan completed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have left the option set to on for periods of a month or so without any repurcussions. Ofcourse I was only running NFS (no iSCSI or FC LUNS).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I read the following TR for more information:&lt;/P&gt;&lt;P&gt;&lt;A href="http://now.netapp.com/NOW/knowledge/docs/olio/guides/pdfs/tr/tr-3679.pdf" target="_blank"&gt;http://now.netapp.com/NOW/knowledge/docs/olio/guides/pdfs/tr/tr-3679.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Supposedly i2p helps with the following (from the tr): &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV id="_mcePaste"&gt;• FPolicy services: FPolicy refers to the storage system’s file policy feature, which provides a flexible &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;way to implement file policies through the use of a specialized off-storage system server. It is an &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;infrastructure that allows external servers to register certain file system events (for example, file open, &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;create, remove, rename, and directory create) and to receive callbacks when these events actually &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;occur on the storage system as a result of a client access. FPolicy events triggered through NFS need &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;the i2p information to report the complete file path to the FPolicy servers. The i2p information is used to &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;convert the inode number reported by the NFS client to a complete file path. &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;• Virus scanning services for UNIX® and NFS clients: External virus scanning servers need a &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;complete file path to check for virus signatures. The i2p feature supplies this file path by converting the &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;inode number provided by NFS clients to a file path. &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;• CIFS ChangeNotify requests: In a multiprotocol environment, the i2p feature allows CIFS change &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;requests to be posted for files that are being accessed by NFS clients for various NFS file operations.&amp;nbsp; &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;• File auditing: Auditing file accesses and other file-related operations requires a complete file path. &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;Some file operations reference a file by its inode number, so the i2p information is required to translate &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;the inode number back to the file path and to record the information for audit purposes. &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;3&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Inode To Pathname (i2p) feature of Data ONTAPDATA ONTAP INTERNAL USE &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;• User-friendly error reporting from within Data ONTAP: Some Data ONTAP error messages &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;present the complete file path for the file instead of an inode number. &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;• Efficient Internal operations: Some Data ONTAP internal operations are faster and more efficient &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;if i2p information is available.&amp;nbsp; &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;• Efficient implementation: I2p provides&amp;nbsp; efficient implementation for some Data ONTAP features.&amp;nbsp; &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;o The dump command in Data ONTAP 7.3 completes faster if the i2p information is &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;available. &lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 18 May 2011 19:18:46 GMT</pubDate>
    <dc:creator>dougsiggins</dc:creator>
    <dc:date>2011-05-18T19:18:46Z</dc:date>
    <item>
      <title>no_i2p volume option</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/no-i2p-volume-option/m-p/47834#M4361</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the recommended value for the no_i2p option for volumes containing LUNs?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The only description I found was this ...&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;If this option is &lt;STRONG&gt;on&lt;/STRONG&gt;, it disables inode to parent pathname translations on the volume. The default setting is &lt;STRONG&gt;off&lt;/STRONG&gt;.&lt;/PRE&gt;&lt;P&gt;What are the consequences if I set this option to "on"?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Brgds&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nicolas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:54:33 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/no-i2p-volume-option/m-p/47834#M4361</guid>
      <dc:creator>CYONGMBH</dc:creator>
      <dc:date>2025-06-05T06:54:33Z</dc:date>
    </item>
    <item>
      <title>Re: no_i2p volume option</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/no-i2p-volume-option/m-p/47838#M4362</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;A while back I ran a bunch of&amp;nbsp; upgrades from 7.0 -- which 7.1 I believe was the first release with i2p. Initially it consumed a large amount of system resources to complete the initial i2p wafl scan. With some of the nodes, this was not bearable, so it was disabled. I have since enabled many of them, and did not notice any significant improvement after the scan completed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have left the option set to on for periods of a month or so without any repurcussions. Ofcourse I was only running NFS (no iSCSI or FC LUNS).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I read the following TR for more information:&lt;/P&gt;&lt;P&gt;&lt;A href="http://now.netapp.com/NOW/knowledge/docs/olio/guides/pdfs/tr/tr-3679.pdf" target="_blank"&gt;http://now.netapp.com/NOW/knowledge/docs/olio/guides/pdfs/tr/tr-3679.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Supposedly i2p helps with the following (from the tr): &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV id="_mcePaste"&gt;• FPolicy services: FPolicy refers to the storage system’s file policy feature, which provides a flexible &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;way to implement file policies through the use of a specialized off-storage system server. It is an &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;infrastructure that allows external servers to register certain file system events (for example, file open, &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;create, remove, rename, and directory create) and to receive callbacks when these events actually &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;occur on the storage system as a result of a client access. FPolicy events triggered through NFS need &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;the i2p information to report the complete file path to the FPolicy servers. The i2p information is used to &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;convert the inode number reported by the NFS client to a complete file path. &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;• Virus scanning services for UNIX® and NFS clients: External virus scanning servers need a &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;complete file path to check for virus signatures. The i2p feature supplies this file path by converting the &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;inode number provided by NFS clients to a file path. &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;• CIFS ChangeNotify requests: In a multiprotocol environment, the i2p feature allows CIFS change &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;requests to be posted for files that are being accessed by NFS clients for various NFS file operations.&amp;nbsp; &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;• File auditing: Auditing file accesses and other file-related operations requires a complete file path. &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;Some file operations reference a file by its inode number, so the i2p information is required to translate &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;the inode number back to the file path and to record the information for audit purposes. &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;3&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Inode To Pathname (i2p) feature of Data ONTAPDATA ONTAP INTERNAL USE &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;• User-friendly error reporting from within Data ONTAP: Some Data ONTAP error messages &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;present the complete file path for the file instead of an inode number. &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;• Efficient Internal operations: Some Data ONTAP internal operations are faster and more efficient &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;if i2p information is available.&amp;nbsp; &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;• Efficient implementation: I2p provides&amp;nbsp; efficient implementation for some Data ONTAP features.&amp;nbsp; &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;o The dump command in Data ONTAP 7.3 completes faster if the i2p information is &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;available. &lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 May 2011 19:18:46 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/no-i2p-volume-option/m-p/47838#M4362</guid>
      <dc:creator>dougsiggins</dc:creator>
      <dc:date>2011-05-18T19:18:46Z</dc:date>
    </item>
    <item>
      <title>Re: no_i2p volume option</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/no-i2p-volume-option/m-p/47846#M4364</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;EM&gt;&lt;EM&gt; &lt;/EM&gt;&lt;/EM&gt;&lt;EM&gt; &lt;/EM&gt;Thanks alot. Your answer was really helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Brgds&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nicolas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 May 2011 07:45:08 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/no-i2p-volume-option/m-p/47846#M4364</guid>
      <dc:creator>CYONGMBH</dc:creator>
      <dc:date>2011-05-19T07:45:08Z</dc:date>
    </item>
  </channel>
</rss>

