<?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 Calling ZAPI volume-set-option for option &amp;quot;maxdirsize&amp;quot; freezes the Filer in Software Development Kit (SDK) and API Discussions</title>
    <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/Calling-ZAPI-volume-set-option-for-option-quot-maxdirsize-quot-freezes-the-Filer/m-p/101116#M1382</link>
    <description>&lt;P&gt;Environment:&lt;/P&gt;&lt;P&gt;NetApp 8.2.2 7-mode running on FAS8040&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have a small utility that creates a volume on the Filer and set a few volume option.&amp;nbsp; We use the .NET SDK to invoke the &amp;lt;volume-create&amp;gt; and &amp;lt;volume-set-option&amp;gt; APIs.&amp;nbsp; When the program runs the &amp;lt;volume-set-option&amp;gt; API with the option "maxdirsize", it will freeze up the API access of the Filer.&amp;nbsp; Any new API connection will stuck in authentication and no more API access to the Filer, including OnCommand.&amp;nbsp; OnCommand will show up as waiting for authentication and after a few minutes it will eventually time out.&amp;nbsp; Eventually we have to reboot the Filer.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then, we open up a SSH connection to the Filer and run the utility again.&amp;nbsp; This time, a message pops up when the program runs the &amp;lt;volume-set-option&amp;gt; API with the option "maxdirsize":&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Warning: The default maximum directory size is model-dependent, and is,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; by default, already optimized for the size of system memory.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; You can increase it for a specific volume by using this option,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; but doing so could impact system performance. This parameter is&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; not supported on Infinite Volumes. Do not proceed unless directed&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; to do so by technical support.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Do you want to continue?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If we don't type anything in the SSH console, the API layer will continue to be stuck.&amp;nbsp; Once we type "yes" in the SSH console, the API layer will work again.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So it looks like there is a really bad bug in the volume-set-option command that it expects an interactive answer even though we are coming in from API.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this a known bug and do we have any information about whether this bug will be addressed?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 26 Feb 2015 16:12:41 GMT</pubDate>
    <dc:creator>Data_Dynamics</dc:creator>
    <dc:date>2015-02-26T16:12:41Z</dc:date>
    <item>
      <title>Calling ZAPI volume-set-option for option "maxdirsize" freezes the Filer</title>
      <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/Calling-ZAPI-volume-set-option-for-option-quot-maxdirsize-quot-freezes-the-Filer/m-p/101116#M1382</link>
      <description>&lt;P&gt;Environment:&lt;/P&gt;&lt;P&gt;NetApp 8.2.2 7-mode running on FAS8040&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have a small utility that creates a volume on the Filer and set a few volume option.&amp;nbsp; We use the .NET SDK to invoke the &amp;lt;volume-create&amp;gt; and &amp;lt;volume-set-option&amp;gt; APIs.&amp;nbsp; When the program runs the &amp;lt;volume-set-option&amp;gt; API with the option "maxdirsize", it will freeze up the API access of the Filer.&amp;nbsp; Any new API connection will stuck in authentication and no more API access to the Filer, including OnCommand.&amp;nbsp; OnCommand will show up as waiting for authentication and after a few minutes it will eventually time out.&amp;nbsp; Eventually we have to reboot the Filer.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then, we open up a SSH connection to the Filer and run the utility again.&amp;nbsp; This time, a message pops up when the program runs the &amp;lt;volume-set-option&amp;gt; API with the option "maxdirsize":&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Warning: The default maximum directory size is model-dependent, and is,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; by default, already optimized for the size of system memory.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; You can increase it for a specific volume by using this option,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; but doing so could impact system performance. This parameter is&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; not supported on Infinite Volumes. Do not proceed unless directed&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; to do so by technical support.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Do you want to continue?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If we don't type anything in the SSH console, the API layer will continue to be stuck.&amp;nbsp; Once we type "yes" in the SSH console, the API layer will work again.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So it looks like there is a really bad bug in the volume-set-option command that it expects an interactive answer even though we are coming in from API.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this a known bug and do we have any information about whether this bug will be addressed?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Feb 2015 16:12:41 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/Calling-ZAPI-volume-set-option-for-option-quot-maxdirsize-quot-freezes-the-Filer/m-p/101116#M1382</guid>
      <dc:creator>Data_Dynamics</dc:creator>
      <dc:date>2015-02-26T16:12:41Z</dc:date>
    </item>
    <item>
      <title>Re: Calling ZAPI volume-set-option for option "maxdirsize" freezes the Filer</title>
      <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/Calling-ZAPI-volume-set-option-for-option-quot-maxdirsize-quot-freezes-the-Filer/m-p/127056#M2231</link>
      <description>&lt;P&gt;I'm currently runnng into the same problem. Did you get a solution for it?&lt;/P&gt;</description>
      <pubDate>Tue, 17 Jan 2017 14:37:19 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/Calling-ZAPI-volume-set-option-for-option-quot-maxdirsize-quot-freezes-the-Filer/m-p/127056#M2231</guid>
      <dc:creator>webtransactor</dc:creator>
      <dc:date>2017-01-17T14:37:19Z</dc:date>
    </item>
  </channel>
</rss>

