<?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 file-create-directory throws EONTAPI_ENOENT after file-get-file-info showed valid info in Software Development Kit (SDK) and API Discussions</title>
    <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/file-create-directory-throws-EONTAPI-ENOENT-after-file-get-file-info-showed/m-p/155316#M3018</link>
    <description>&lt;P&gt;i've encountered an issue on ontap9, that looks like this:&lt;/P&gt;
&lt;P&gt;1. i create dir1 using&amp;nbsp;file-create-directory&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2. i call file-get-file-info for dir1, and get a valid info back (with size and name etc).&lt;/P&gt;
&lt;P&gt;3. i try to call file-create-directory for "dir1/child" and get&amp;nbsp;EONTAPI_ENOENT&amp;nbsp; (meaning dir1 doesn't exit)&lt;BR /&gt;4. after a ~30sec i'm able to do a successful file-create-directory for "/dir1/child"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;why is this happening and is there an elegant way to be certain when "dir1" actually fully exists as far as netapp is concerned?&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 11:14:20 GMT</pubDate>
    <dc:creator>eladgotfrid1</dc:creator>
    <dc:date>2025-06-04T11:14:20Z</dc:date>
    <item>
      <title>file-create-directory throws EONTAPI_ENOENT after file-get-file-info showed valid info</title>
      <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/file-create-directory-throws-EONTAPI-ENOENT-after-file-get-file-info-showed/m-p/155316#M3018</link>
      <description>&lt;P&gt;i've encountered an issue on ontap9, that looks like this:&lt;/P&gt;
&lt;P&gt;1. i create dir1 using&amp;nbsp;file-create-directory&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2. i call file-get-file-info for dir1, and get a valid info back (with size and name etc).&lt;/P&gt;
&lt;P&gt;3. i try to call file-create-directory for "dir1/child" and get&amp;nbsp;EONTAPI_ENOENT&amp;nbsp; (meaning dir1 doesn't exit)&lt;BR /&gt;4. after a ~30sec i'm able to do a successful file-create-directory for "/dir1/child"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;why is this happening and is there an elegant way to be certain when "dir1" actually fully exists as far as netapp is concerned?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 11:14:20 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/file-create-directory-throws-EONTAPI-ENOENT-after-file-get-file-info-showed/m-p/155316#M3018</guid>
      <dc:creator>eladgotfrid1</dc:creator>
      <dc:date>2025-06-04T11:14:20Z</dc:date>
    </item>
    <item>
      <title>Re: file-create-directory throws EONTAPI_ENOENT after file-get-file-info showed valid info</title>
      <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/file-create-directory-throws-EONTAPI-ENOENT-after-file-get-file-info-showed/m-p/157050#M3052</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You should be able to see the dir created almost instantly. As why you running into this issue, will need to review some logs and maybe have you collect a packet trace to check why the filer is not able to create the file/directory into the newly created one. If you still facing that issue, you can create a case and have support assist in troubleshooting this behaviour.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jun 2020 02:17:21 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/file-create-directory-throws-EONTAPI-ENOENT-after-file-get-file-info-showed/m-p/157050#M3052</guid>
      <dc:creator>hmoubara</dc:creator>
      <dc:date>2020-06-17T02:17:21Z</dc:date>
    </item>
  </channel>
</rss>

