<?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: inode utilization in Active IQ Unified Manager Discussions</title>
    <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/inode-utilization/m-p/30559#M6287</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Naresh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have done this task often depend on the nature of our application. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Would say there is performance hit but not big enough for me to notice, or in another word, I have to increase the number of inodes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Glen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 07 Jan 2014 14:39:36 GMT</pubDate>
    <dc:creator>GLENYU5820</dc:creator>
    <dc:date>2014-01-07T14:39:36Z</dc:date>
    <item>
      <title>inode utilization</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/inode-utilization/m-p/30554#M6286</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Frequently we are getting the alerts for inode utilization, My question is increase the maxfile size limit on volume will have any performance inpact..?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 05:46:12 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/inode-utilization/m-p/30554#M6286</guid>
      <dc:creator>NARESH_NASAM</dc:creator>
      <dc:date>2025-06-05T05:46:12Z</dc:date>
    </item>
    <item>
      <title>Re: inode utilization</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/inode-utilization/m-p/30559#M6287</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Naresh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have done this task often depend on the nature of our application. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Would say there is performance hit but not big enough for me to notice, or in another word, I have to increase the number of inodes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Glen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Jan 2014 14:39:36 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/inode-utilization/m-p/30559#M6287</guid>
      <dc:creator>GLENYU5820</dc:creator>
      <dc:date>2014-01-07T14:39:36Z</dc:date>
    </item>
    <item>
      <title>Re: inode utilization</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/inode-utilization/m-p/30564#M6288</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am assuming you are using 7 mode, there are ways, but they have caveats&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is a rule for this, you can increase the base by 20% once, then increase total by 20% once again.&amp;nbsp; After this second time, it is not recommended to increase again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.netapp.com/support/index?page=content&amp;amp;actp=LIST&amp;amp;id=1010377" target="_blank"&gt;https://kb.netapp.com/support/index?page=content&amp;amp;actp=LIST&amp;amp;id=1010377&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You must be very careful here however.&amp;nbsp; NDMP jobs of any type are notoriously sensitive to inode counts.&amp;nbsp; This means that backups and ndmpcopy will take longer on the same size volume once you increase the inode count.&amp;nbsp; Also snapvault and qtree snapmirror jobs are affected by increasing inodes as there is an ndmp component.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once you increase the count, there is really no way to ever go back.&amp;nbsp; So if you find you have performance issues, there is only one fix - migrate the data to other volumes using host based copies, destroy the volume.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me state out in the open, I have done the 20/20 increase many times and have not really seen major problems outside the backup times increasing.&amp;nbsp; I have also had my team be forced to go beyond the 20/20 increase and seen a controller taken down by simply running an "ls" which is the Unix equivalent of "dir".&amp;nbsp; The guidelines are in place for a very good reason and should be followed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lastly there used to be a bug that volumes over 1TB in size did not have the inode count calculated properly.&amp;nbsp; It was not scheduled to be fixed, if this is a large volume, you may have to do the required calculations and set the inodes to the proper count for your volume size. The bug ID is &lt;A href="http://web.netapp.com/~burt/views/199/199233.html" style="color: #0067c5; font-family: Arial, Helvetica, sans-serif; font-size: 12px; background-color: #ffffff;" target="_blank"&gt;199233&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Scott&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Jan 2014 16:00:47 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/inode-utilization/m-p/30564#M6288</guid>
      <dc:creator>cscott</dc:creator>
      <dc:date>2014-01-07T16:00:47Z</dc:date>
    </item>
  </channel>
</rss>

